Overview

Spinwheel supports payer verification using a Plaid processor token, allowing clients to verify a payer's bank account without requiring micro-deposit verification.

Using a Plaid token can significantly reduce verification time and improve the user experience for ACH payment flows.

📘

Why use Plaid verification?

Traditional ACH verification through micro-deposits can take 1–3 business days. Plaid token verification allows bank account ownership to be verified during the payer creation process, enabling faster ACH payment initiation and reducing user drop-off.

Supported Payment Types

Plaid token verification is currently supported for:

• ACH payments

Prerequisites

Before creating a payer with Plaid verification:

1. Your Plaid integration must have Tabapay enabled
2. The end user must successfully complete a Plaid Link session.
3. Your application must exchange the Plaid public token for a processor token.
4. The processor token must be generated for the bank account that will be used for ACH payments.

Request Parameters

When creating a payer, include the following additional fields in the request:

Example Request

{
  "firstName": "John",
  "lastName": "Doe",
  "email": "[email protected]",
  "paymentMethod": {
    "routingNumber": "021000021",
    "accountNumber": "123456789",
    "tokenType": "PLAID",
    "token": "processor-sandbox-123456789"
  }
}

Verification Flow

1. User selects a bank account through Plaid Link.

2. Your application exchanges the Plaid public token for a Plaid processor token.

3. Your application calls the Create a Payer endpoint and provides:

   • tokenType: "PLAID"
   • token: "<plaid_processor_token>"

4. Spinwheel validates the token and verifies ownership of the bank account.

5. The payer can immediately be used for ACH payment initiation without waiting for micro-deposit verification.

Fallback Behavior

If tokenType and token are not provided, payer verification continues to use the existing verification workflow. This enhancement is fully backward compatible with existing integrations.

Important Considerations

• The provided token must be a valid Plaid processor token. If invalid, the payer will need to get recreated after the user has corrected the processor token in Plaid Link.
• The processor token must correspond to the same bank account being registered as the payer's funding source.
• Existing payer creation workflows remain unchanged if a Plaid token is not supplied.
• Recurring ACH payments created from a verified payer continue to follow existing payment processing rules.

Sandbox Testing

When testing in the sandbox environment:

1. Generate a Plaid processor token using Plaid's sandbox environment.
2. Provide the processor token in the token field.
3. Set tokenType to PLAID.
4. Verify the payer is created successfully and can be used for ACH payment creation.