2.85.92 ProntoPayments v2

Owned by Posimente
Last updated: Nov 14, 2023 by Eva Mae Seno
2 min read

Release Date: 26/4/2023

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

 

Important Reminder

  • This version has a known issue with the following description:

    • Payment Source having a not 'Active' tag when created via Manage Payment Source in Opportunity. 

    • The newly created Payment Source will not automatically populate the Payment Source field in Opportunity.

    • Credit Card number is fully shown in the Credit Card Number fields having an API name ASPHPP__token_Card_Number__c and ASPHPP__Card_Number_c.

  • This issue affects 2.85.91 to 2.85.102. 

  • Version 2.85.103 (click here) resolves this issue. If you prefer not to upgrade at this time due to other factors, a workaround would be creating an automation that sets the Payment Source to active. This ensures that the card information is encrypted.

 Upgrade Risks

Make sure WIT components are passing the encrypted session ID and make sure to re-save existing gateway records to have the password field encrypted.   

 Post Configuration

Add Remote Site setting if you want use process payment eWay gateway  

To add a remote site setting: 

  1. From Setup, enter Remote Site Settings in the Quick Find box, then select Remote Site Settings

  2. Click New Remote Site

  3. Enter a descriptive term for the Remote Site Name

    1. CloudFlare 

    2. ApiDBIp 

  4. Enter the URL for the remote site

    1.  https://www.cloudflare.com

    2. https://api.db-ip.com 

  5. Optionally, enter a description of the site. 

  6. Click Save. 

Generate ABA File 

  • When generating a bank ABA file by clicking the Generate ABA File button on the PP Payment Batch record detail page, 

    • If the Bank ABA Format field from the ProntoPayments Settings custom setting is equal to NZ Format,

      • After the ABA File is generated: 

        • A Bank ABA File will be generated and linked to the PP Payment Batch record. 

          • The NZ file format will be followed

          • If the value of the Payment Transaction’s/PPayment’s Payment Reference field is greater than 12 string characters, 

          • On the generated Bank ABA File, the Originator Reference columns (5th and 7th) are populated based on the last 12 string characters of the Payment Reference field

        • If the value of the Payment Transaction’s/PPayment’s Payment Reference field is equal to or lesser than 12 string characters,

          • On the generated Bank ABA File, the Originator Reference columns (5th and 7th) are populated based on the exact value of the Payment Reference field .

Payment Source record 

  • When creating a non-tokenised Bank Account Payment Source record,

    • Regardless of whether the Bank Account BSB field is empty or not but the Bank Account Number field is populated,

      • A non-tokenised Bank Account Payment Source record will be successfully created. 

Process payment via Button and Batch 

  • If the gateway is eWay

    • The API request body is added the CustomerIP object the value is Ip Address of the user. 

Process Reusable Component 

  • If the gateway is eWay

    • The API request body is added the CustomerIP object the value is Ip Address of the user.

Payment Transaction and PPayment record creation 

  • IF the record type is NOT one of the values in the Payment Type (e.g. Cash, Cheque, Bank, Card) do not override.