Cmn4 Payment

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

Version Type Description ID

19.0.1.0

 ENH A new context property, Maximum Payment Amount has been added under Cmn4/Payment. It sets the maximum payment amount allowed by the transit agency. It must be set in the base unit of the currency used, for example, cents for Canadian dollars. We recommend that this property not be set to more than a few hundred dollars as an additional guard to prevent failed payment attempts. Note that the more restrictive value between this property and the payment processor specific values is used. In other words, the value set for this property does not override the maximum values set by the payment processors. TI-10586

19.0.1.0

 ENH DB-schema change: A new table, Cmn4PaymentResponseCode has been added. It stores the raw response codes, which payment processors supply in the response from calls to process payments. The codes provide the specific reasons that payments did not go through. The table contains the following fields:
  • paymentId - Unique identifier for a single payment.
  • codeType - The type of code from the payment processor. Examples include response code and approval code.
  • code - Code from the payment processor.
 TI-10715

19.0.1.0

 ENH Db-schema change: A new table, Cmn4PaymentQueueContract has been added. This is an internal table used to store payment contracts that have not yet been fulfilled. It has one field, paymentId - Unique identifier for a single payment. TI-10844
19.0.2.0 ENH Cmn4 Payment now supports the logging of requests and responses including the filtering of sensitive data for Chase Paymentech in a safe and reliable manner. TI-10524

19.0.2.0

 ENH A new Admin page has been added to allow administrators to view and search through the payment information. They can search the information using filters such as date range and payment status and sort the search results, for example, by Payment Id. They can also choose to print the search results if necessary. TI-10770

19.0.2.0

 ENH DB-Schema change: New tables have been added to be able to generate Order ID values for Chase Paymentech: Cmn4PaymentTransaction, Cmn4PaymentAuthorisation, and Cmn4PaymentAuthorisationDetail. The order ID values have to be unique for the payment and authorization requests. Since the paymentId has been used as the orderId, a new table is needed to store the transactionId, which can be used as the orderId. New payments will use the transactionId as the paymentId. The fields of the Cmn4PaymentTransaction table are: transactionId, transactionType, requester, and created (This refers to the date and time.) The fields of the Cmn4PaymentAuthorisation table are: transactionId, status, modified,externalReferenceId (This refers to transaction type.), and approvalCode. The fields of the Cmn4PaymentAuthorisationDetail table are: transactionId and amount. TI-11110

19.0.2.0

 ENH DB-Schema changes:
  1. A new table, Cmn4PaymentChaseProfile has been added to store profiles for Chase Paymentech. The table has the following fields: internalProfileId (This is a unique identifier for a given payment profile within Trapeze.), paymentType, and PaymentSubtype. (These correspond to the appropriate Chase fields.)
  2. In the Cmn4PaymentAuthorisation table, the "approvalcode" field has been renamed "authorisationCode." It contains the authorization code from the financial institution.
 TI-11174

19.0.2.0

 ENH DB-Schema changes: Changes were made on currency-related fields in three tables to support the change from using double to float data type for currency values. (This means changing to the use of integers.) The tables and their fields that have been updated are:
  1. Cmn4PaymentDetail - The data type of the field, amountRequested has been changed from Double to SLong.
  2. Cmn4Payment - The data type of the field, amountCharged has been changed from Double to SLong.
  3. Cmn4PaymentAuthorisationDetail - The field name of amount has been changed to amountRequested.
 TI-11238

19.0.3.0

 ENH DB-schema change: To be consistent with the paymentId in the Payment tables, the following changes have been made:
  • Cmn4PaymentAuthorisation and Cmn4PaymentAuthorisationDetail tables - Renamed transactionId field to authorisationId.
  • Added foreign keys which reference Cmn4PaymentTransaction.transactionId
 TI-11690

The task is related to TI-11111.

19.0.3.0

 ENH For transit sites using Paymentus with their EZ-Wallet account, a Reload button has been added to the Add balance screen. It allows users to retrieve their payment profiles again when one or more of these profiles fail to load.

In addition, some changes were made to the Add credit card screen (used when Chase Paymentech is the payment provider): card type drop-down list hidden, size has been adjusted, and the client's name now automatically filled in.

 TI-10417

19.0.11.0

ENH As part of the work on transactional payment profile creation, the following changes have been made to support transactions for all external page requests:

The following table has been deleted: Cmn4PaymentProfileAuthNet

The following new tables that will store information regarding external profile page requests as well as the results have been added:
  • Cmn4PaymentExtPage - Stores basic, mutable information about external pages.
  • Cmn4PaymentExtPageDetail - Stores immutable details about external pages.
  • Cmn4PaymentExtProfilePage - Stores information specific to external profile pages.
The following tables have been updated - The 'internalProfileId' field has been replaced with 'paymentProfileId.'
  • Cmn4PaymentProfile
  • Cmn4PaymentProfileUser
  • Cmn4PaymentChaseProfile
  • Cmn4PaymentDetail

(This task is associated with TI-15066.)

TI-15671
19.0.20.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