Starknet: USDC On/OffRamp live.   Details →
Sphere Paysphere

Customer

A Customer is a user or business that is associated with your application. Customers are parties that use your application to send and receive transfers securely.

A Customer represents either an individual user or a business entity within your application. Every transfer is tied to a customer, ensuring that transactions are traceable, compliant, and secure.

The customer object and its unique customer_id are required for all API requests. This allows Spherepay to correctly identify the customer, link related activities, and apply the appropriate compliance checks.

Ensuring that each customer is unique and undergoes the proper onboarding process is critical for:

  • Preventing fraud and malicious activities
  • Meeting regulatory requirements such as KYC/AML
  • Building trust between your business and end-users
  • Ensuring smooth transfers without delays or rejections

Customer Registration

Customer registration is the first step in enabling transfers. At a high level, the registration ensures that:

  1. The customer is correctly created and tracked in the system
  2. They explicitly agree to the platform’s Terms of Service (TOS)
  3. They complete required Know Your Customer (KYC) checks before initiating transfers

Customer Registration Flow


Registration Flow

The customer registration process follows these broad steps:

  1. Merchant creates a customer
    → via POST /customer API
  2. Merchant requests Terms of Service (TOS) link
    → via POST /customer/:customer_id/tos-link
  3. Merchant displays TOS page to the user
  4. User accepts TOS
  5. Merchant requests KYC link
    → via POST /customer/:customer_id/kyc-link
  6. Merchant displays KYC page to the user
  7. User completes KYC
  8. Merchant checks customer status
    → via GET /customer/:customer_id

For step-by-step implementation details, refer to the Customer Registration Guide.


Why This Matters

Customer onboarding is not just a formality—it underpins the security and compliance of the payment network.

  • For Developers: The process ensures your API calls will always have a valid customer_id that passes compliance checks.
  • For Businesses: It protects your company from fraud, ensures you remain compliant with regulatory standards, and reassures customers that their funds are safe.