PosiPay 1.10

Package URL:

Post-Deployment Configuration

1. Delete the following fields (if not already auto-removed):

   • Gateway Account → Default Stripe API Version. (This can only be done if your org’s PosiGive package is version 1.15.)

   • PosiPay Settings (Custom Setting) → Stripe API Version

2. Update all existing Gateway Account records:

   • Select the correct Stripe API Version matching the connected Stripe account.

   • Perform reauthentication.

3. If a Stripe API version is missing from the Stripe API Version global picklist value set:

   • Manually add it before setting the Gateway Account.

4. Grant Guest User access permission to the Stripe API Version field.

What’s New

• With Stripe’s Basil API version, new objects and processes related to invoices were introduced. These changes impacted PosiPay’s invoice workflow. To support the new API structure, a new object has been created to handle invoice payment details, ensuring seamless integration with both PosiPay and PosiGive.

• An error occurred when generating a gateway customer using the Stripe form, the process completed successfully, but no Gateway Customer record was created. Additionally, the gateway event status was incorrectly marked as Failed, causing discrepancies in the PosiPay flow.

  This issue has been fixed. Now, when the process completes successfully, a Gateway Customer record is created and Gateway Events are processed without errors.

• PosiPay now supports configurable Stripe API versions for Gateway Accounts. A new Stripe API Version picklist field has been added, allowing you to specify which Stripe API version should be used in API callouts. If a value is selected, PosiPay will use that version. If left blank, PosiPay will automatically default to the latest supported Basil API version (2025-07-30.basil).
  The following fields has been removed from the respectives objects:

  • Gateway Account – Default Stripe API Version

  • PosiPay Settings (Custome Setting) – Stripe API Version