Account Numbers

Account Numbers provide access to verified ACH account and routing numbers for Accounts. These numbers enable money movement operations such as direct deposits and withdrawals.

Link to this section#Overview

To access Account Numbers:

1. Enable the Account Numbers product in your Connector configuration
2. Have the end-user connect their institution through the Connector
3. Subscribe to the account.verified webhook to be notified when numbers are available
4. Retrieve the ACH numbers via the REST API using your API Secret Key

Link to this section#REST Operations

ACH numbers are only available via server-to-server calls from the REST API and there is no GraphQL query for account numbers at this time. This is a security measure to ensure sensitive data is only accessed server-side with proper authentication.

Link to this section#Endpoint

GEThttps://api.quiltt.io/v1/accounts/{accountId}/ach_numbersCopy endpoint URL to clipboard

Link to this section#Authentication

This endpoint requires authentication with an API Secret Key (via Bearer token) or a Processor Token (via Basic auth).

Link to this section#Error Responses

Link to this section#GraphQL Queries

While ACH numbers are only available via REST, you can check the verification status of accounts via GraphQL:

The verified field indicates whether the account has been verified for money movement and ACH numbers are available.

Link to this section#Webhooks

Link to this section#account.verified

The account.verified event fires when an account becomes verified for money movement and ACH numbers become available via the Platform API.

Link to this section#Security Considerations

• Account numbers are considered Sensitive Customer Information under various regulations. Implement appropriate data retention policies and ensure compliance with applicable frameworks (GLBA, SOC 2, etc.).

Link to this section#Best Practices

• Logging: Never log full account numbers. If logging is necessary, mask all but the last 4 digits.
• Storage: Store account numbers only when necessary. Use encrypted storage (AES-256 or equivalent).
• Transmission: Always use TLS 1.2 or higher for API calls.
• Payment Processors: Consider using a trusted Payment Processor like Straddle for handling money movement operations. Straddle provides a secure, compliant platform for processing bank payments using Quiltt's Processor Tokens.