2.85.119 ProntoPayments v2

Owned by Cherry Mae Descallar, created
Last updated: May 20, 2024 by Dale Brown
4 min read

Release Date: 17/05/2024

URL: /packaging/installPackage.apexp?p0=04tIU000001E7VU

 

Important Notice

  • When using Purchase Transaction Type for payment processing via Process Payment button or Batch Payment Processing, CVV/CVC/CNV is required but it will not be saved in the eWay portal as per PCI Compliance. In version 2.85.113, we will not save the CVV/CVC/CNV as part of the PCI Compliance.

  • We advise using the Purchase Transaction Type for once-off payments where we will input the CVV/CVC/CNV for payment transactions.

Upgrade Risks

When upgrading to version 2.71 or higher, make sure to re-save existing gateway records to have the password field encrypted .

 

Enhancements

  • eWay Transaction Type Settings in Gateway Record Level

    • When creating/updating a Gateway record,

      • If the Record Type equals eWay, the Transaction Type field value is based on the Gateway’s ECH Gateway Name field where the Transaction Types (ECH Gateway Name) are MOTO and Purchase

  • eWay Transaction Type - Manage Payment Source

    • When creating/updating a tokenised Credit Card Payment Source record,

      • If the Gateway has a Record Type equals eWay and their Transaction Type (ECH Gateway Name) equals to MOTO OR EMPTY,

        • The Card CVV field is NOT a required field

      • If the Gateway has a Record Type equals eWay and their Transaction Type (ECH Gateway Name) equals to Purchase,

        • The Card CVV field is a required field

  • eWay Transaction Type - Payment Processing

    • When processing a Credit Card payment via the Process Payment button in an Opportunity/PPayment record,

      • If the Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = MOTO OR EMPTY,

        • If using a non-tokenised Credit Card Payment Source record,

          • The payment will be processed where the Transaction Type is MOTO and uses Credit Card details with CVN (optional), Expiry Month and Expiry Year

        • If using a tokenised Credit Card Payment Source record,

          • The payment will be processed where the Transaction Type is MOTO and uses a token with CVN (optional), Expiry Month and Expiry Year

      • If the Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = Purchase,

        • If using a non-tokenised Credit Card Payment Source record,

          • The payment will be processed where the Transaction Type is Purchase and uses Credit Card details with CVN (required), Expiry Month and Expiry Year

        • NOTE: If using a tokenised Credit Card Payment Source record, it will return EWAY_CARDCVN Required response. It requires to input CVN again as CVN will not stored in their portal when creating a Customer Token as part of PCI Compliance.

    • When processing a Credit Card payment via the Batch Payment Processing in the ProntoPayments Settings → Scheduler,

      • If the Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = MOTO OR EMPTY,

        • If using a non-tokenised Credit Card Payment Source record,

          • The payment will be processed where the Transaction Type is MOTO and uses Credit Card details with CVN (optional), Expiry Month and Expiry Year

        • If using a tokenised Credit Card Payment Source record,

          • The payment will be processed where the Transaction Type is MOTO and uses a token with CVN (optional), Expiry Month and Expiry Year

      • If the Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = Purchase,

        • If using a non-tokenised Credit Card Payment Source record,

          • The payment will be processed where the Transaction Type is Purchase and uses Credit Card details with CVN (required), Expiry Month and Expiry Year

        • NOTE: If using a tokenised Credit Card Payment Source record, it will return EWAY_CARDCVN Required response. It requires to input CVN again as CVN will not stored in their portal when creating a Customer Token as part of PCI Compliance.

    • When processing a payment via the test flow that invokes the Reusable Component,

      • If the Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = MOTO OR EMPTY,

        • If using Credit Card details,

          • The payment will be processed where the Transaction Type is MOTO and uses Credit Card details with CVN (optional), Expiry Month and Expiry Year

        • If using a token,

          • The payment will be processed where the Transaction Type is MOTO and uses a token with CVN (optional), Expiry Month and Expiry Year

      • If the Gateway has a Record Type = eWay and their Transaction Type (ECH Gateway Name) = Purchase,

        • If using Credit Card details,

          • The payment will be processed where the Transaction Type is Purchase and uses Credit Card details with CVN (required), Expiry Month and Expiry Year

        • NOTE: If using a tokenised Credit Card Payment Source record, it will return EWAY_CARDCVN Required response. It requires to input CVN again as CVN will not stored in their portal when creating a Customer Token as part of PCI Compliance.