Receivers
People or businesses that will receive payments or stablecoins.
What is a receiver?
A receiver is an individual or business entity designated to interact with BlindPay.
For compliance and regulatory requirements, every customer on your platform must be registered as a receiver in BlindPay. This is a mandatory step to ensure proper transaction tracking and reporting. If any of your customers operate as money transmitters (entities that transfer funds on behalf of others), they are also required to register their end customers as receivers in the system. This multi-level registration ensures complete transparency throughout the payment chain.
You can attach multiple bank accounts and blockchain wallets to a receiver.
Compliance and KYC
Every receiver is required to go through a KYC process to verify their identity.
These are the data we collect for every receiver type
(business, individual) and receiver kyc_type
(standard, enhanced):
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* |
KYC Enhanced
Everything from KYC/B standard, plus:
All individuals on Enhanced KYC will be manually verified by BlindPay compliance team. This process can take up to 24 hours.
Individual |
---|
Source of Funds Document Type |
Source of Funds Document File |
Individual Holding Document Front File |
Purpose of Transactions |
Purpose of Transactions Explanation |
All fields with a *
are optional.
Review Timeline
The time it takes to review and approve a receiver's KYC/KYB submission varies depending on the verification type:
Verification Type | Review Timeline |
---|---|
KYC Standard | 30 seconds |
KYC Enhanced | 3 hours to 2 business days |
KYB Standard | 3 hours to 2 business days |
KYC Statuses
Every receiver has a KYC status that indicates the current state of their verification process. The status can be one of the following:
verifying
: The receiver's KYC is currently being processedapproved
: The receiver's KYC has been successfully verified and approvedrejected
: The receiver's KYC has been rejected
Status Flow
When you create a receiver, the status will automatically be set to verifying
. The status update timeline depends on the KYC type:
- KYC Standard: After approximately 30 seconds, the status will typically be updated to either
approved
orrejected
automatically. However, in some cases where our compliance team needs to review the submission manually, the status will remainverifying
until our team manually approves or rejects it. - KYC Enhanced & KYB Standard: These always require manual review by our compliance team, so the status will remain
verifying
until our team completes the review process.
KYC Warnings
When a receiver's KYC is rejected, BlindPay provides feedback in the kyc_warnings
field. This field contains information about why the KYC was rejected, which can help you understand what needs to be corrected.
To retry the KYC process after a rejection, you'll need to create a brand new receiver with the corrected information. You cannot update an existing receiver's KYC information.
Payout & Payin Limits
The transfer limits are calculated based on the stablecoin amount being transferred. Each receiver has separate limits for both payouts (sending funds) and payins (receiving funds).
Note: These limits are set for compliance purposes and can be increased upon submission of additional documentation.
KYC Standard | KYB Standard | KYC Enhanced | |
---|---|---|---|
Per transaction | 10,000 | 30,000 | 50,000 |
Daily | 50,000 | 100,000 | 100,000 |
Monthly | 100,000 | 250,000 | 500,000 |
Creating a receiver
You can check the required fields in the BlindPay API Docs.
Before creating a receiver, you need to:
- Create an account on BlindPay
- Create a development instance
- Create your API key
- Get tos_id from terms of service acceptance
Remember: replace YOUR_SECRET_TOKEN
with your API key and in_000000000000
with your instance ID.
Testing scenarios
By default all the receivers created in 'development' instances are automatically approved, however if you want them to be Rejected, you can can use 'Fail' as the first name or legal name for individuals and businesses respectively.