/
PosiPay 1.6

PosiPay 1.6

URL package: /packaging/installPackage.apexp?p0=04tOZ0000004jRZYAY

What’s New

  • The Gateway Settlement Reconciliation batch process has been updated to properly handle decimal conversions. Previously, an error could occur when converting whole number amounts (especially with negative values) into decimal format. With this fix:

    • All Gateway Settlement records, whether containing positive or negative amounts, will now be reconciled without errors.

    • The system now safely converts amounts to decimals, ensuring accurate and consistent reconciliation results across all records.

  • When tokenizing credit card or BECS debit payment details using the Stripe customer form, the system now correctly links the Account record to the Payment Instrument record (for NPC), if an Account record is defined.

    Gateway Event records are first created for the webhook payloads received for the customer and the payment method. Then, a Gateway Customer record is either created or updated if a match already exists. This record includes key details from the payload such as the Customer ID, Customer Name, Email, Phone, and links to the relevant Account and Gateway Account.

    If the org has the NPC standard Payment Instrument object enabled, a corresponding Payment Instrument record is created or updated.

  • A new field called Refund Reason has been added to the Gateway Transaction record. This field will store the reason for the refund, if provided.
    When a partial or full payment refund is processed, the system handles it correctly whether or not a refund reason is provided.

    If a refund reason is included, the system records the refund along with the reason. A Gateway Event is created, and a Gateway Transaction record is added with a record type of Refund. The Refund Reason field is filled with the provided reason, and the rest of the transaction details are captured from the webhook data. This refund transaction is also linked to the original payment transaction. On the Stripe dashboard, the refund activity will clearly show the reason for the refund.

    If no reason is provided, the refund still processes successfully. A Gateway Event and a Gateway Transaction record are also created with a record type of Refund, but in this case, the Refund Reason field is left empty. The remaining transaction fields are still populated from the webhook data, and the refund is linked to the original transaction. In Stripe, the refund will be shown, but the reason field will be blank.