Initiate Verification

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
🚧

Valid Statuses

A new verification may only be started when the external account's verification_status is unverified. If a verification is in progress or has already been completed, a 422 response will be returned.

📘

Debit and credit capabilities must be enabled to attempt the verification

In order to perform micro-deposit verification, the internal account that is used must have both credit and debit capabilities enabled. This is because the micro-deposits are sent and then immediately retrieved. If the internal account is missing any one of the debit and credit capabilities, the verification will not be attempted and the micro-deposits will not be sent.

Path Params
string
required
Body Params
string
required

The ID of the internal account where the micro-deposits originate from. Both credit and debit capabilities must be enabled.

string
required

ach, eft, and rtp are supported payment types. Note that rtp micro-deposits will collected via ACH debit.

string

Defaults to the currency of the originating account.

string

The payment type used to create the micro-deposit if the original payment type is not valid for the receiving account. Currently, this only supports falling back from RTP to ACH (payment_type=rtp and fallback_type=ach).

string

Controls the speed of ACH transfers used in the verification flow. Either normal or high. For ACH payments, high represents a same-day ACH. Default value is normal if left blank. Note: This field applies even when payment_type is rtp, as the debit/callback still uses ACH to recover the funds.

Response

Language
Credentials
Basic
base64
:
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json