Swipelux

Update customer information

Update customer information like phone number, email, etc.

For complete API specification including request/response schemas and interactive examples, see the API Reference.

Overview

Update existing customer information including contact details and KYC data.

Path Parameters

ParameterTypeDescription
idstringThe customer ID to update

Additional Parameters

shareToken (optional)

Type: string

Description: A SumSub share token that allows importing existing KYC verification data for crypto rails customer management.

When you update a customer with a shareToken from SumSub, their KYC data will be automatically fetched and imported for crypto rails operations. This PUT method is specifically designed for the crypto rails workflow where:

  • Customers are created first: Create customer with minimal data {}
  • ShareTokens are added via PUT: Each time a new token is generated at SumSub
  • Short TTL management: Tokens expire quickly, requiring repeated PUT updates
  • Crypto rails requirement: KYC verification is mandatory for crypto transfers

This approach significantly improves the user experience by:

  • Eliminating redundant verification: Customers don't need to re-verify their identity
  • Faster crypto rails processing: KYC status is immediately available for transfer creation
  • Higher conversion rates: Reduced friction leads to better completion rates
  • Token refresh capability: Handle token expiration seamlessly with new PUT calls

Crypto Rails Integration Pattern

Typical Workflow:

  1. Create Customer: POST /v1/customers with minimal data
  2. Generate SumSub Token: Obtain shareToken from SumSub with short TTL
  3. Update Customer: PUT /v1/customers/{id} with shareToken in body
  4. Token Refresh: Repeat PUT with new shareToken when current one expires

Integration Notes

  • Generate the shareToken from your SumSub integration before making each PUT request
  • The shareToken must be valid and associated with completed KYC verification data
  • Important: Due to short TTL, you'll need to make multiple PUT calls as tokens expire
  • This pattern is specifically designed for crypto rails where KYC verification is required for transfers
  • Each PUT call can include other customer data updates alongside the shareToken
  • Learn more about the complete SumSub integration workflow in our KYC Management guide

On this page