Customer APIs are in preview as part of USD Virtual Accounts.
id when you request customer-scoped products such as a USD virtual account.
Customer records are general Yara resources. They live in this section because USD Virtual Accounts
is the first product that requires customer verification.
How ownership works
A customer does not receive an API key or a separate Yara ledger balance. You manage any customer
balance shown in your product. Yara keeps the customer ID as attribution on customer-scoped activity.
Create a customer
Send a uniqueexternal_reference that links the Yara customer to the customer in your system.
Individual customers require first_name and last_name.
id. Resource IDs are always scoped to your authenticated merchant
account. A request for a customer owned by another merchant returns 404.
Yara returns 201 Created when provisioning completes immediately. If the provider result is
temporarily uncertain, Yara returns the same durable customer in PROVISIONING with
202 Accepted. Keep its id and poll GET /v1/customers/{customer_id}; do not create another
customer. A retry with the same idempotency key returns the original status and body.
Customer email is unique across Yara’s customer namespace, while external_reference is unique
within your merchant account.
Read customers
UseGET /v1/customers to list customers. You can filter by external_reference, type, status,
or creation time. Use GET /v1/customers/{customer_id} to retrieve one customer.
Customer responses include only authorized customer fields and normalized verification state.
Yara protects identity and verification data at rest.
Next step
Verify a customer
Submit the verification required before creating a USD virtual account.