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

IndividualBusiness
First nameLegal name
Last nameTax ID (government id number)
Date of birthFormation date
EmailEmail
CountryCountry
Tax ID (government id number)Doing business as*
Phone number*Website*
IP AddressIP Address
CountryCountry
Address 1Address 1
Address 2*Address 2*
CityCity
State/province/regionState/province/region
Postal codePostal code
ID Document - CountryUBOS + 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 - FrontProof 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:

Individual
Source of Funds Document Type
Source of Funds Document File
Individual Holding Document Front File
Purpose of Transactions
Purpose of Transactions Explanation

Review Timeline

The time it takes to review and approve a receiver's KYC/KYB submission varies depending on the verification type:

Verification TypeReview Timeline
KYC Standard30 seconds
KYC Enhanced3 hours to 2 business days
KYB Standard3 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 processed
  • approved: The receiver's KYC has been successfully verified and approved
  • rejected: 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 or rejected automatically. However, in some cases where our compliance team needs to review the submission manually, the status will remain verifying 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).

KYC StandardKYB StandardKYC Enhanced
Per transaction10,00030,00050,000
Daily50,000100,000100,000
Monthly100,000250,000500,000

Creating a receiver

You can check the required fields in the BlindPay API Docs.

Before creating a receiver, you need to:

  1. Create an account on BlindPay
  2. Create a development instance
  3. Create your API key
  4. Get tos_id from terms of service acceptance
cURL
curl --request POST \
  --url https://api.blindpay.com/v1/instances/in_000000000000/receivers \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
    "type": "individual",
    "kyc_type": "standard",
    "email": "[email protected]",
    "tax_id": "12345678",
    "address_line_1": "8 The Green",
    "address_line_2": "#12345",
    "city": "Dover",
    "state_province_region": "DE",
    "country": "US",
    "postal_code": "02050",
    "ip_address": "127.0.0.1",
    "phone_number": "+1234567890",
    "proof_of_address_doc_type": "UTILITY_BILL",
    "proof_of_address_doc_file": "https://pub-4fabf5dd55154f19a0384b16f2b816d9.r2.dev/v4-460px-Get-Proof-of-Address-Step-3-Version-2.jpg.jpeg",
    "first_name": "John",
    "last_name": "Doe",
    "date_of_birth": "1998-01-01T00:00:00Z",
    "id_doc_country": "US",
    "id_doc_type": "PASSPORT",
    "id_doc_front_file": "https://pub-4fabf5dd55154f19a0384b16f2b816d9.r2.dev/1000_F_365165797_VwQbNaD4yjWwQ6y1ENKh1xS0TXauOQvj.jpg"
  }'

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.