Overview
ACH is a great way for customers to pay for their services using their bank account. When setting up an ACH payment on the account, a customer usually enters these details themselves through the portal. When doing so, they usually login directly to their bank account to allow Stripe to verify and ensure the bank account details are correct and there are no issues.
However, there may be times a user cannot login to their bank account and needs to manually enter the bank account details, does not have instant verification enabled on their bank account or a user within gaiia needs to add these details. In these cases, Stripe requires an additional verification process. This process is called micro deposits and involves posting one or two very small deposits on the customer's bank account.
This document will outline how to manage this process directly in gaiia and the micro deposit process in a bit more detail.
ACH Payment Verification Process
As outlined above, Stripe uses a micro deposit process to verify the authenticity of the bank account being provided, in cases where it cannot be instantaneously verified. As the name suggests, the deposits are used to ensure that the bank is actually valid and can be used for payments. These deposits can occur in one of two ways:
- A single deposit (usually just $0.01) is added to the bank account with a unique code in the description (SM-XXXXX). The customer or a user within gaiia will then need to enter this code to verify the account.
- Two small deposits of the same or differing amounts are added to the bank account with a clear identifier it is Stripe. The customer or a user within gaiia will then need to enter both amounts to verify the account.
Regardless of how the deposits occur, the general process that occurs is as follows:
- A user within gaiia or a customer, enters the bank account details.
- The payment method is added in a "Requires verification" status in gaiia.
- An email is sent to the customer to notify that the bank account requires further verification. This email will contain:
- An explanation of the process.
- When the customer can expect the micro deposit to occur in their bank account.
- A url to allow them to enter the necessary details.
- At the specified date, the micro deposit occurs (using one of the methods outlined above).
- A customer using the provided URL in the email or a user directly within gaiia can then enter the code or amounts to verify the bank account.
Managing ACH Payment Verification
While the section above outlined the general process, this section, will outline how to manage this directly within gaiia.
Identifying a Payment that Requires Verification & Verifying It
Any ACH payment method that requires or currently going through micro deposit verification can be identified by the "Requires verification" tag shown directly on it.
From here, a user can click on the options menu of the payment method and verify it directly in gaiia, on behalf of the customer. A window, depending on which micro deposit process is required, will appear allowing the user to complete it.
If verified successfully, this will remove the "Requires verification" status on the payment method and it will be available for use in one-time and auto payments.
Customer Notification
A user within gaiia can verify the method, but a customer will likely complete this process. Once a payment method is added that requires verification, an automated communication is immediately sent out to them notifying them of the process that is required.
A new template has been added called "Bank account verification" for this notification. Like all communication within gaiia, it can be fully customized and, by default, includes all necessary merge tags to ensure the right details are provided to the customer.
Tracking Payment Verifications
gaiia also provides reporting to track all payments being verified across all of the customers. Within the "Account Payment Methods" report under the "Billing" category, use the "ACH Payments Requiring Additional Verification" & "ACH Payments Failing Verification" to review these details.
Related to