What it is
A customer is an individual or business entity designated to interact with BlindPay. You can attach multiple bank accounts, blockchain wallets, and BlindPay-managed wallets to a customer.
How it works
For compliance and regulatory requirements, every customer on your platform must be registered as a customer in BlindPay. This is mandatory for transaction tracking and reporting. If any of your customers operate as money transmitters (entities that transfer funds on behalf of others), they must also register their end customers as customers in the system. This multi-level registration ensures complete transparency throughout the payment chain.
Every customer must complete a KYC process to verify their identity before sending or receiving funds.
Required fields
We collect the following data per customer type (business, individual) and kyc_type (standard, enhanced). Fields marked with * are optional.
KYC/B Standard
| Individual | Business |
|---|---|
| First name | Legal name |
| Last name | Tax ID (government id number) |
| Date of birth | Formation date |
| Country | Country |
| Tax ID (government id number) | Doing business as* |
| Phone number | Website* |
| IP Address | IP Address |
| Country | Country |
| Address 1 | Address 1 |
| Address 2* | Address 2* |
| City | City |
| State/province/region | State/province/region |
| Postal code | Postal code |
| ID Document - Country | UBOS + Shareholders above 25% (everything from Standard KYC but no Phone and IP Address) |
| ID Document - Type (passport, id card, drivers license) | Company Formation Document |
| ID Document - Front | Proof of Ownership Document |
| ID Document - Back* | Proof of Address - Type* |
| Proof of Address - Type (utility bill, bank statement)* | Proof of Address - Document* |
| Proof of Address - Document* | |
| Selfie File |
KYC Enhanced — everything from KYC/B Standard, plus:
| Individual |
|---|
| Source of Funds Document Type |
| Source of Funds Document File |
| Purpose of Transactions |
| Purpose of Transactions Explanation |
All customers from high risk countries must go through Enhanced KYC. Enhanced KYC individuals are manually verified by BlindPay's compliance team — this can take up to 1 business day and may require additional documents.
For document quality and submission guidelines, see KYC Basics.
Review timeline
| Verification Type | Review Timeline |
|---|---|
| KYC Standard | ~60 seconds |
| KYC Enhanced | 3 hours to 1 business day |
| KYB Standard | 3 hours to 1 business day |
Statuses
Every customer has a KYC status indicating the current state of their verification:
verifying: KYC is being processedapproved: KYC verified and approvedrejected: KYC rejectedcompliance_request: compliance team opened a Request for Information and is waiting for additional documents or clarifications
On creation the status is verifying. The update timeline depends on the KYC type:
- KYC Standard: after ~60 seconds the status typically becomes
approvedorrejectedautomatically. When our compliance team needs to review manually, it staysverifyinguntil they decide. - KYC Enhanced & KYB Standard: always require manual review, so the status stays
verifyinguntil review completes.
When KYC is rejected, BlindPay returns feedback in the kyc_warnings or fraud_warnings field explaining what to correct. To retry after a rejection, create a brand new customer with corrected information — you cannot update an existing customer's KYC information.
Limits
Transfer limits are calculated on the stablecoin amount transferred. Each customer has separate limits for payouts (sending) and payins (receiving).
| KYC Standard | KYB Standard | KYC Enhanced | |
|---|---|---|---|
| Per transaction | US$ 10,000 | US$ 30,000 | US$ 50,000 |
| Daily | US$ 50,000 | US$ 100,000 | US$ 100,000 |
| Monthly | US$ 100,000 | US$ 250,000 | US$ 500,000 |
Note: These limits are set for compliance purposes and can be increased upon submission of additional documentation using this API endpoint.
Prerequisites
Create a customer
You can check the required fields in the BlindPay API Docs.
YOUR_SECRET_TOKEN with your API key and in_000000000000 with your instance ID. Testing scenarios
By default all customers created in development instances are automatically approved. To test a rejection, use Fail as the first name (individuals) or legal name (businesses).