What are SaaS Account to Account Payments?

Account to account (A2A) payments in a SaaS subscription billing environment are a method of direct electronic funds transfer from the customer’s bank account to the software vendor’s treasury without the help of any card network intermediaries. 

SaaS application payment systems under such arrangements function mainly in two separate customer checkout and billing methods: pay-by-bank checkout and persistent recurring debits.

Here is a side-by-side comparison of the two concepts:

Initiating an account to account financial transaction involves a programmatic process within banking infrastructures, leading to treasury settlement:

• Initiate: When a user chooses the “Pay-by-Bank” option or a recurring invoice is set, the SaaS payment platform, backed by an open banking aggregator or payment gateway, initiates the payment request.
• Authenticate: The user logs into their bank portal or app securely and uses biometrics or multi-factor tokens to verify their identity.
• Clear: Assuming there are no issues, regional financial networks will carry out the clearing and settlement instructions communication directly between the systems.
• Settle: This is the actual time when the money is withdrawn from the customer’s demand deposit account and credited to the software vendor’s bank ​‍​‌‍​‍‌​‍​‌‍​‍‌account.

Adding an innovative Pay-by-Bank checkout flow to the core billing system you already have requires coordinating software engineering and financial event management.

1. Set up very clear subscriber payment notifications to dynamically remind customers three days before the automatic bank debit run date (an example).
2. Add a mobile banking redirection element to your checkout user interface to maintain the highest initial conversion.
3. Keep the core billing engine webhooks integrated and continuously updated with bank transaction changes. 

Since bank transfers do not always happen in near real-time, these transaction webhooks are vital to make sure that your SaaS monthly subscription platform grants user access to the SaaS platform when payments settle or revokes their accounts when a transaction ​‍​‌‍​‍‌​‍​‌‍​‍‌fails.

Payment processing costs may be improved through direct bank payments. However, engineering teams and product leaders should carefully evaluate implementation considerations and balance them against the long-term benefits. Key areas to consider include:

• Customer Adoption and Experience: Customers are highly accustomed to entering card details during checkout. The shift to bank app authorization presents a modified payment process, potentially requiring user education and iterative design to enhance the user experience and foster trust.
• Bank APIs: Aggregators facilitate connectivity to a diverse banking ecosystem for A2A payment networks, but this arrangement may introduce complexity. The extent of integration varies among institutions; however, continuous standardization and ecosystem maturity are associated with changes in reliability and coverage.