{"title":"Upgrade guide — v19 to v20 — Payments","slug":"upgrade-guide-v19-to-v20-payments","url":"https://support.storeconnect.com/articles/upgrade-guide-v19-to-v20-payments","url_markdown":"https://support.storeconnect.com/articles/upgrade-guide-v19-to-v20-payments.md","subtitle":null,"summary":"Upgrade steps for stores adopting new payment gateways or changing payment configuration in v20, including CyberSource, Tyro, TouchNet, and ACH payment behavior changes.","type":"Release_Notes","video_url":"","keywords":null,"last_modified":"2026-08-21T07:12:35+0000","body_markdown":"Review this section if you are adopting a new payment gateway or changing payment configurations in v20.\n\n\n## Review: New payment gateways\n\nv20 adds support for the following payment gateways. No action is required unless you intend to adopt one of these providers. See [Payment providers](payment-providers) for an overview of all supported gateways.\n\n| Gateway | Support added | Reference |\n|---|---|---|\n| CyberSource | Standard checkout and express checkout | [Cybersource](cybersource-payment-provider) |\n| Tyro | Standard payment capture | [Tyro](tyro-payment-provider) |\n| TouchNet | Payment capture | — |\n\n\n## Review: Existing gateway updates\n\nIf you use any of the gateways below, review the updated behavior in a sandbox before upgrading production.\n\n| Gateway | Change | Reference |\n|---|---|---|\n| eWay v2 | Subscription payments now supported | [Eway](eway-payment-provider) |\n| Braintree | Salesforce-managed payments now supported | [Braintree](braintree-payment-provider) |\n| Stripe ACH | Payments now begin as Pending and poll for settlement confirmation | [Stripe ACH](stripe-ach-payment-provider) |\n| Authorize.Net ACH | Payments now begin as Pending and poll for settlement confirmation | [Authorize.Net ACH](authorize-net-ach-payment-provider) |\n| Amazon Pay | Explicit Stripe payment support added | — |\n\n\n## Behavior changes\n\n### Review: ACH payment polling\n\nStripe ACH and Authorize.Net ACH payments now begin in a pending state and poll for settlement confirmation, rather than treating the payment as complete immediately. If you have automation or reporting that acts on ACH payment status, review those workflows to ensure they account for the pending state. See [Stripe ACH](stripe-ach-payment-provider) and [Authorize.Net ACH](authorize-net-ach-payment-provider) for full documentation.\n\n\n### Review: Payment replay attack protection\n\nAdditional replay attack protection has been added for gateways that do not natively finalize transactions. No configuration is required. Review any custom payment processing flows that might be affected by stricter duplicate-detection logic.\n\n\n### Review: Payment fingerprint\n\nA new `Payment__c.Fingerprint__c` field has been added. For manual payments, this field is automatically populated. No action is required unless you want to include the fingerprint field in page layouts or reporting."}