Cmn4 Payment

Release notes on tasks that apply to the Cmn4 Payment module.

Version Type Description ID
21.2.0.0 ENH The following context properties have been added to support echecks/direct deposit (ECP) for Chase:
  • Cmn4/Payment/ChasePaymentech/External Profile Page/Account Type/ - This has two options: Credit Card (default) and ECP.
  • Cmn4/Payment/ChasePaymentech/Orbital Hosted Payment/Form/ECP/Confirm Routing Number
  • Cmn4/Payment/ChasePaymentech/Orbital Hosted Payment/Form/ECP/Confirm Account Number
 TI-16310
21.2.0.0 ENH Db-Schema change: A new table, Cmn4PaymentAdminProfile_ACT has been added as part of the action logging for payment admin actions. It stores audit actions involving profiles made by payment admins and contains the following fields: auditId, auditAction, and paymentProfileToken. TI-18074
21.3.1.0 ENH Db-schema change: A new field, topupType has been added to the Cmn4PaymentDetail table. It allows users to specify the top up payment type: manual or auto. (This is required to pass the correct MITMsgType value in requests involving payment profiles for the Chase payment system.) TI-18774
21.3.1.0 ENH The required elements to Cmn4 Payment have been added to ensure that the Trapeze payment solution integration with CHASE meets their certification requirements. A new context property was added: Cmn4/Payment/ChasePaymentech/Secondary Service Address. (This address is used when the primary url isn't working.) TI-18372
21.5.0.0 ENH DB-Schema: A new table, Cmn4PaymentCustomer has been created to store customer object information, which is required for the CyberSource implementation. The fields are:
  • amountCharged
  • customerId
  • details
  • externalReferenceId - Unique identifier given by the payment processor, if the processor/method provides it.
  • id - Name of the third party method being called. If no specific method is being called, an identifier beginning with an underscore should be used.
  • paymentType - Corresponds to Chase's payment_type field.
  • processorCustomerId - Unique Identifier for this customer that is provided by the payment processor
  • product
  • productName - Identifier for a given module or component (for example 'PASS' or 'TransitNow')
 TI-19633
21.6.0.0 ENH The following context properties applied to the payment process have been updated:
  • Cmn4/Payment/CyberSource/Service Address: Service address that is used for CyberSource calls. (Use https://apitest.cybersource.com for testing and https://api.cybersource.com for production.)
  • Cmn4/Payment/CyberSource/MerchantId: Merchant Id that is assigned by CyberSource
The following related context properties have been added:
  • Cmn4/Payment/CyberSource/Public Key
  • Cmn4/Payment/CyberSource/Secret Key: Keys that are generated through the CyberSource dev center
  • Cmn4/Payment/CyberSource/Secure Acceptance Checkout/Profile Id
  • Cmn4/Payment/CyberSource/Secure Acceptance Checkout/Public Key
  • Cmn4/Payment/CyberSource/Secure Acceptance Checkout/Secret Key
 TI-19784
21.8.0.0 CORR Fixed an issue where only All option appeared in Payment Status drop-down list on the EZ-Wallet Payment List page. TI-19315
21.8.0.0 ENH Visa Cybersource Secure Acceptance Checkout API was implemented for Cmn4 Payment to create payment instruments. TI-19295
21.8.0.0 ENH The DeleteProfile method for Visa Cybersource was added to Cmn4Payment. TI-18920
21.12.0.0 ENH Updated the Cmn4PaymentAdminProfileReconciliationCompare method to support CyberSource. TI-20271
21.12.0.0 CORR Fixed an issue where CR and CZ account types for Chase were not supported and profiles could not be saved. TI-20118
21.18.0.0 CORR

There was an issue where Payment Instrument Id was being returned in a different field than before. The old account had it returned in the transaction_id, whereas now it’s being returned in the payment_token field.

Now, a new context property was added: Cmn4/Payment/CyberSource/Secure Acceptance Checkout/Payment Instrument Id Field. This will allow you to specify which cybersource response field has the Payment Instrument Id, so this issue occurrs again, you can just update the context property.

 MODTE-634