ACH via Stripe: Drop In Guide
Integrate ACH via Stripe on your website or mobile application with just a few lines of code.
Before you begin
This guide assumes that you know how to
Accept payments with ACH via Stripe
Prepare the client session
ACH via Stripe requires the following data to process a payment successfully. Pass the following data in the client session, or in the payment request (for manual payment creation).
Parameter Name | Required | Description |
---|---|---|
currencyCode | ✓ | 3-letter currency code in ISO 4217 format. For ACH via Stripe, only USD is supported. |
order ↳ lineItems | ✓ | Details of the line items of the order |
metadata | ✓ | In order to have ACH via Stripe successful, you need to pass your device info: IP address and user agent in the metadata.metadata.deviceInfo.ipAddress and metadata.deviceInfo.userAgent |
paymentMethod | ✓ |
That should be passed if one wishes to vault ACH via Stripe.
Prepare the SDK for payments
Show Universal Checkout
Pass device info when creating the client session ACH via Stripe requires that a mandate is accepted before the payment is completed.
Mandates that are accepted online require IP address and user-agent of the device that the payment is made from.
Specify this information when creating the client session, otherwise payments will remain in Pending state.
Universal Checkout
ACH via Stripe is automatically presented to the customer when calling Primer.showUniversalCheckout
with the Stripe publishable key set up.
Additionally, ACH via Stripe requires to show a Mandate to the user. You can either pass the full mandate text yourself via SDK options, or pass a merchant name and rely on the mandate text Primer provides you with.
Customization
Check the customization guide to learn how to customize payment method buttons.
Show Universal Checkout
Pass device info when creating the client session ACH via Stripe requires that a mandate is accepted before the payment is completed.
Mandates that are accepted online require IP address and user-agent of the device that the payment is made from.
Specify this information when creating the client session, otherwise payments will remain in Pending state.
Universal Checkout
ACH via Stripe is automatically presented to the customer when calling Primer.showUniversalCheckout
with the Stripe publishable key set up.
Additionally, ACH via Stripe requires to show a Mandate to the user. You can either pass the full mandate text yourself via SDK options, or pass a merchant name and rely on the mandate text Primer provides you with.
Customization
Check the customization guide to learn how to customize payment method buttons.
Pre-requisites
Pass device info when creating the client session
ACH via Stripe requires that a mandate is accepted before the payment is completed.
Mandates that are accepted online require IP address and user-agent of the device that the payment is made from.
Specify this information when creating the client session, otherwise payments will remain in Pending state.
Define the Primer Stripe dependency
In order to be able to use ACH via Stripe you will have to install PrimerStripeSDK
which is available via CocoaPods.
Define the Stripe publishable key and mandate information
It is important that you specify your Stripe publishable key along with mandate information when creating PrimerSettings
, otherwise you’ll encounter errors at app runtime.
ACH via Stripe requires that a mandate is displayed before the payment is completed. This mandate will display automatically once a bank account is chosen.
The drop-in implementation provides two ways for customizing the mandate.
- you specify only your business’s name and the SDK will use a predefined template:
By clicking Accept, you authorize [Business Name] to debit the selected bank account for any amount owed for charges arising from your use of [Business Name]‘s services and/or purchase of products from [Business Name], pursuant to [Business Name]‘s website and terms, until this authorization is revoked. You may amend or cancel this authorization at any time by providing notice to [Business Name] with 30 (thirty) days notice. If you use [Business Name]‘s services or purchase additional products periodically pursuant to [Business Name]‘s terms, you authorize [Business Name] to debit your bank account periodically. Payments that fall outside the regular debits authorized above will only be debited after your authorization is obtained.
- you specify the entire body of the mandate:
Proceed with the SDK initialization:
Show Universal Checkout
ACH via Stripe payment method is automatically presented to the customer when calling Primer.shared.showUniversalCheckout(clientToken: self.clientToken)
.
Show Universal Checkout
ACH via Stripe is automatically presented to the customer when calling Primer.shared.showUniversalCheckout
.
Customization
Check the customization guide to learn how to customize payment method buttons.
Pre-requisites
Pass device info and payment type when creating the client session ACH via Stripe requires that a mandate is accepted before the payment is completed. Mandates that are accepted online require IP address and user-agent of the device that the payment is made from.
Specify this information when creating the client session, otherwise payments will remain in Pending state.
Define the Primer Stripe dependency
Amend the dependencies section of your app’s build.gradle
to include Primer’s stripe-android
library:
Define the Stripe publishable key and mandate information
It is important that you specify your Stripe publishable key along with mandate information when instantiating PrimerSettings
, otherwise you’ll encounter errors at app runtime.
ACH via Stripe requires that a mandate is displayed before the payment is completed. This mandate will display automatically once a bank account is chosen.
The drop-in implementation provides two ways for customizing the mandate.
- you specify only your business’s name and the SDK will use a predefined template: By clicking Accept, you authorize [Business Name] to debit the bank selected bank for any amount owed for charges arising from your use of [Business Name]‘s services and/or purchase of products from [Business Name], pursuant to [Business Name]‘s website and terms, until this authorization is revoked. You may amend or cancel this authorization at any time by providing notice to [Business Name] with 30 (thirty) days notice. If you use [Business Name]‘s services or purchase additional products periodically pursuant to [Business Name]‘s terms, you authorize [Business Name] to debit your bank account periodically. Payments that fall outside the regular debits authorized above will only be debited after your authorization is obtained.
- you specify the entire body of the mandate as a string resource:
- you specify the entire body of the mandate as a string:
Proceed with the SDK initialization:
The default onFailed implementation of PrimerCheckoutListener
will emit unlocalized error messages provided by the Stripe SDK. You’re welcome to override the function to suit your specific needs.
For a more comprehensive understanding, refer to the documentation available for the PrimerCheckoutListener
interface and to the Initialize Universal Checkout section in the Get started guide.
Show Universal Checkout
ACH via Stripe is automatically presented to the customer when calling Primer.instance.showUniversalCheckout
.
Show Universal Checkout
ACH via Stripe is automatically presented to the customer when calling Primer.instance.showUniversalCheckout
.
Customization
Check the customization guide to learn how to customize payment method buttons.
Pre-requisites
Pass device info and payment type when creating the client session
ACH via Stripe requires that a mandate is accepted before the payment is completed. Mandates that are accepted online require IP address and user-agent of the device that the payment is made from.
Specify this information when creating the client session, otherwise payments will remain in Pending state.
Define the Primer Stripe dependency
Android
Amend the dependencies section of your app’s build.gradle
to include Primer’s stripe-android
library:
iOS
Add the dependency to your Podfile
:
Define the Stripe publishable key and mandate information
It is important that you specify your Stripe publishable key along with mandate information when instantiating PrimerSettings
, otherwise you’ll encounter errors at app runtime.
ACH via Stripe requires that a mandate is displayed before the payment is completed. This mandate will display automatically once a bank account is chosen.
The drop-in implementation provides two ways for customizing the mandate.
- you specify only your business’s name and the SDK will use a predefined template: By clicking Accept, you authorize [Business Name] to debit the selected bank account for any amount owed for charges arising from your use of [Business Name]‘s services and/or purchase of products from [Business Name], pursuant to [Business Name]‘s website and terms, until this authorization is revoked. You may amend or cancel this authorization at any time by providing notice to [Business Name] with 30 (thirty) days notice. If you use [Business Name]‘s services or purchase additional products periodically pursuant to [Business Name]‘s terms, you authorize [Business Name] to debit your bank account periodically. Payments that fall outside the regular debits authorized above will only be debited after your authorization is obtained.
- you specify the entire body of the mandate: Use
fullMandateText
to specify the full mandate text for both iOS and Android. On Android,fullMandateStringResourceName
will be used instead if provided.
Proceed with the SDK initialization:
The default onError listener will emit unlocalized error messages provided by the Stripe SDK. You’re welcome to override the function to suit your specific needs.
For a more comprehensive understanding, refer to the configuration documentation and to the Initialize Universal Checkout section in the Get started guide.
Show Universal Checkout
ACH via Stripe is automatically presented to the customer when calling Primer.showUniversalCheckout
.
Customization
Check the customization guide to learn how to customize Universal Checkout.
Go live
You don’t need to do anything particular to go live — just make sure to use production credentials.
Show Universal Checkout
ACH via Stripe is automatically presented to the customer when calling Primer.showUniversalCheckout
.
Customization
Check the customization guide to learn how to customize payment method buttons.
Vaulting
When creating client session, vaultOnAgreement
flag should be passed, along with paymentType
:
Note that the vaultOnAgreement flag is supported starting with API version 2.4.
In order to vault ACH via Stripe accounts, pass the following data in the Client Session:
Parameter Name | Required | Description |
---|---|---|
customerId | ✓ | A unique identifier for your customer |
Minimum version of Web SDK: 2.47.0.
ACH via Stripe payment tokens can be vaulted automatically on successful agreement if the vaultOnAgreement
flag is turned on when creating the client session.
Minimum version of Web SDK: 2.47.0.
ACH via Stripe payment tokens can be vaulted automatically on successful agreement if the vaultOnAgreement
flag is turned on when creating the client session.
Minimum version of iOS SDK: 2.33.0.
ACH via Stripe payment tokens can be vaulted automatically on successful agreement if the vaultOnAgreement
flag is turned on when creating the client session.
Minimum version of iOS SDK: 2.33.0.
ACH via Stripe payment tokens can be vaulted automatically on successful agreement if the vaultOnAgreement
flag is turned on when creating the client session.
Minimum version of React Native SDK: 2.28.0.
ACH via Stripe payment tokens can be vaulted automatically on successful agreement if the vaultOnAgreement
flag is turned on when creating the client session.
Test
You can test payments using USD as the currency.
Sandbox testing
- After selecting the payment method button in the Checkout, the page will navigate to a form
- After you complete the form, the Stripe pop-up will appear
- After finishing the steps inside the Stripe pop-up, the user will be taken back to the Checkout to confirm / decline mandate
- At the end of this flow, the payment status will be first PENDING in the Primer Dashboard and depending on the user actions or external factors, like insufficient funds in the bank account, it will be either DECLINED, CANCELLED or SETTLED for successful completion in Primer Dashboard
- To simulate the receiving of funds and transition the payment to SETTLED, you can choose in the Stripe pop-up:
Test Institution
andSuccess
account in the next screen. Next you will be taken back to Checkout to confirm the mandate. Primer will receive a webhook and subsequently update the payment to SETTLED.
Go Live
You don’t need to do anything particular to go live — just make sure to use production credentials.