Purpose

The Customers resource stores a tokenized version of a customer's bank routing number, account number, and name. tokenization replaces those sensitive values with a surrogate "token" that cannot be reversed if intercepted. Because routing numbers identify the financial institution and account numbers identify the individual account, both must be protected.

When to Use

Create a Customer once for each checking or savings account you intend to debit or credit. After you have the customer_uuid, you can:

• Initiate payments (debits) or payouts (credits) without ever sending raw bank data again.
• Send prenotifications: zero-dollar ACH entries used to verify account details before the first live transaction.

How It Works

1. POST /customers with the customer's name, routing number, and account number.
2. Vericheck encrypts the payload at rest and returns a customer_uuid.
3. All subsequent calls (/payments, /payouts, /prenotes) take that customer_uuid instead of raw bank details.
4. You may optionally update non-sensitive metadata (e.g. email) via PATCH /customers/{customer_uuid}.

Vericheck also fingerprints each bank account so duplicate entries are prevented.