Customers

Customers represent users of your business in the Inflow Connect ecosystem. By registering your customers with Inflow Connect, you can enable seamless transfers of stablecoins or fiat currencies from or to your customers' wallets or bank accounts. All KYC and KYB checks are handled by Inflow Connect so you can safely move funds, knowing that Inflow Connect has properly vetted your users in compliance with legal requirements.

When you register a new customer with Inflow Connect, we must collect key information such as name and email, along with unique identifiers such as SSN, EIN/TIN, or government ID number. This information allows Inflow Connect to properly KYC/KYB and approve the customer before initiating any transactions.

See Compliance for detailed compliance requirements and verification processes.

Prerequisites: A customer must be approved before you can create accounts or initiate payments for them.

Customer Types

Inflow Connect supports two types of customers:

• INDIVIDUAL: Personal accounts for individual users
• BUSINESS: Business accounts for companies and organizations

KYC/KYB Process

Customer creation includes identity verification through our KYC (Know Your Customer) and KYB (Know Your Business) process:

1. Create Customer → Submit basic information and get customerId
2. KYC Verification → Customer completes identity verification via provided link
3. Approval → Customer is approved and can transact
4. Account Creation → Create accounts for the approved customer

Create Customer

All customers are created through the KYC verification link endpoint, which automatically handles compliance requirements.

Endpoint: POST /customer/kyx-verification-link

Individual Customer

curl -X POST https://api.inflowconnect.com/customer/kyx-verification-link \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "[email protected]",
    "customerType": "INDIVIDUAL",
    "redirectUrl": "https://yourapp.com/verification-complete",
    "individualInfo": {
      "firstName": "John",
      "lastName": "Doe"
    }
  }'

Business Customer

curl -X POST https://api.inflowconnect.com/customer/kyx-verification-link \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "[email protected]",
    "customerType": "BUSINESS",
    "redirectUrl": "https://yourapp.com/verification-complete",
    "businessInfo": {
      "businessName": "Acme Corporation"
    }
  }'

Response

Both requests return the same response structure:

{
  "verification_url": "https://verify.inflowconnect.com/kyc/abc123...",
  "customerId": "cus_a1b2c3d4e5f6g7h8"
}

Response Fields:

• verification_url: Direct link for customer to complete KYC verification
• customerId: Unique identifier for the customer (use for all subsequent API calls)

Customer Verification Flow

1. Share Verification Link: Provide the verification_url to your customer
2. Customer Completes KYC: Customer submits required documents and information
3. Compliance Review: Inflow Connect reviews and approves the customer
4. Webhook Notification: You receive approval status via webhook (optional)
5. Ready for Transactions: Customer can now create accounts and transact

Documentation Requirements

All customers must provide identity verification documents during the KYC/KYB process:

For Individual Customers:

• Government-issued photo ID, tax ID, proof of address
• See Requirements for Individuals for complete documentation and country-specific details

For Business Customers:

• Business registration, beneficial ownership, control person documentation
• See Requirements for Businesses for complete documentation and UBO requirements

See Compliance for verification status flows, processing times and more.

Customer Management

Get Customer Details

curl -X GET https://api.inflowconnect.com/customer/{customerId} \
  -H "Authorization: Bearer YOUR_API_KEY"

List All Customers

curl -X GET https://api.inflowconnect.com/customer \
  -H "Authorization: Bearer YOUR_API_KEY"

Important Notes

Email Uniqueness

• Each email address can only be associated with one customer
• Attempting to create duplicate customers with the same email will fail
• Use unique email addresses for each individual or business entity

KYC Status Monitoring

• Monitor customer approval status via webhooks
• Poll customer details endpoint for status updates
• Customers cannot transact until fully approved

Compliance Updates

• Additional documentation may be requested during review
• Re-verification may be required for high-value transactions
• Maintain current customer information for ongoing compliance