Customers

Overview

The Customers feature lets you onboard your business end-users to LINK, enabling them to move stablecoins or fiat between their wallets and bank accounts securely and in compliance with regulations.

❔

Who needs this?

Only businesses that serve business customers (KYB) need to integrate this flow. If you only serve individual end-users (KYC), you don’t need to use the Customers API.

What LINK handles for you

• KYC/KYB: LINK manages identity and business verification through our compliance provider.

• Compliance gating: Transactions are only allowed after a customer is approved.

• Status & audit trail: KYB progress and outcomes are visible on the Bridge Dashboard for your compliance team.

Key concepts

Typical flow

1. Your server calls Create Business Customer (Customers API).
2. LINK returns a customer_id and kyb_link_url.
3. You send the link to your business customer (via email or dashboard CTA).
4. The customer completes KYB in the hosted verification flow.
5. KYB status updates appear in the Bridge Dashboard and through the Customers API.

📘

NOTE: To view the document types and examples your end-users must submit, refer to the Compliance page .

Implementation notes

• KYB link delivery: You can email the kyb_link_url directly to your customer or display it in your dashboard with a “Complete Verification” button.
• Link expiration: Some links may expire after a set period. Always fetch the latest kyb_link_url using Get Customer if a user reports an expired or invalid link.
• Polling or webhooks: Poll Get Customer until the status is approved.
• Idempotency (recommended): Use an idempotency key when creating a customer to prevent duplicates if a request is retried.
• Dashboard visibility: All KYB details and outcomes are visible in your Bridge Dashboard for full auditability.