This is a checklist that a fintech can run through before launching to assess overall readiness
Below is a list of steps you would typically need to complete before launching in production with a basic payments use case (Account opening, ACH, and Wires). They all might not be required depending on your use case and partner bank.
Getting started
Share funds flow with bank partner for review/approval
Account Opening
Understand the sequence of API calls required to create an account as outlined in our account creation guide.
KYC/KYB
Account Management
Payments
ACH
Understand the lifecycle of originating an ACH, outlined in our ACH guide.
To expedite testing, leverage our ACH simulations in sandbox.
Wires
pending
until the next processing window opens.Cards
First, determine the types of card products you will be leveraging based on your use case and timelines: virtual, physical, and/or digital wallets. Virtual and physical cards can be implemented relatively quickly, while digital wallets can take longer due to the approvals needed from the bank, the network, and Apple/Google. Most customers will launch with virtual/physical cards to start and add digital wallets at a later point in time.
Card art templates will be shared once you kick off with your partner bank. It is important to return completed card art assets as quickly as possible, as this is what kick-starts the card implementation process. Review/approval of your card assets will be required by: your bank, the network, and/or the card printer as applicable.
Managing risk
Card management - activation, renewal, suspension, termination.
It is important to understand what each card event means and the corresponding transactions. A couple of important examples to understand are auth-standin and force-capture.
Controls to consider:
Please refer to our compliance toolkit with guidance on how to handle cardholder disputes. You will need to work with your partner bank to establish a bank-approved process.
Please leverage our Card simulations in sandbox for testing.
Book Transfers
Webhooks
Storage & Logging
Partners
Compliance toolkit review
Transaction Monitoring
Request Production Access from your partner bank. You will need to ensure:
Subscribe to our status page
Support portal access: We strongly recommend utilizing our support portal for increased visibility across your team and easier case management.
Provide contact information for notifications:
This is a checklist that a fintech can run through before launching to assess overall readiness
Below is a list of steps you would typically need to complete before launching in production with a basic payments use case (Account opening, ACH, and Wires). They all might not be required depending on your use case and partner bank.
Getting started
Share funds flow with bank partner for review/approval
Account Opening
Understand the sequence of API calls required to create an account as outlined in our account creation guide.
KYC/KYB
Account Management
Payments
ACH
Understand the lifecycle of originating an ACH, outlined in our ACH guide.
To expedite testing, leverage our ACH simulations in sandbox.
Wires
pending
until the next processing window opens.Cards
First, determine the types of card products you will be leveraging based on your use case and timelines: virtual, physical, and/or digital wallets. Virtual and physical cards can be implemented relatively quickly, while digital wallets can take longer due to the approvals needed from the bank, the network, and Apple/Google. Most customers will launch with virtual/physical cards to start and add digital wallets at a later point in time.
Card art templates will be shared once you kick off with your partner bank. It is important to return completed card art assets as quickly as possible, as this is what kick-starts the card implementation process. Review/approval of your card assets will be required by: your bank, the network, and/or the card printer as applicable.
Managing risk
Card management - activation, renewal, suspension, termination.
It is important to understand what each card event means and the corresponding transactions. A couple of important examples to understand are auth-standin and force-capture.
Controls to consider:
Please refer to our compliance toolkit with guidance on how to handle cardholder disputes. You will need to work with your partner bank to establish a bank-approved process.
Please leverage our Card simulations in sandbox for testing.
Book Transfers
Webhooks
Storage & Logging
Partners
Compliance toolkit review
Transaction Monitoring
Request Production Access from your partner bank. You will need to ensure:
Subscribe to our status page
Support portal access: We strongly recommend utilizing our support portal for increased visibility across your team and easier case management.
Provide contact information for notifications: