KYC Import

Swipelux supports various patterns of KYC data sharing between Swipelux and partners:

1. Partner could provide SumSub share token to import KYC data from the partner. User will have to pass simplified KYC process (usually just a liveness check) afterwards.
2. Partner could pre-upload photos of some documents when partner's KYC provider is not SumSub. User will have to pass full KYC process, but without re-uploading documents.
3. Swipelux could provide user's KYC data to partner as SumSub share token.

Option (2) is available for any connected partner. Please contact Swipelux if you would like to use options (1) or (3).

Providing SumSub share token to Swipelux

To start this kind of flow, you should first export a share token from the SumSub service. You should consult SumSub API documentation for details of the procedure. Use swipelux.com_21030 as the client ID.

Orders with KYC sharing could be initiated from backend side only. You should make POST request to /api/orders/createPrepared endpoint, specifying order amounts, user phone and providing KYC share token:

// POST /api/orders/createPrepared
// Authorization: Bearer xxx
// Content-Type: application/json
 
{
  "amounts": {
    "from": {
      "amount": "100",
      "currency": "USD"
    },
    "to": {
      /* specify "amount" field here if you want to do reverse calculation */
      /* "amount": "0.05" */
      "currency": "BTC"
    }
  },
  "shareToken": "xxxxxxxxx",
  "user": {
    "phone": "+0123456789",
    "email": "user@example.com"
  },
  /* optional field for your own order identifier in free form */
  "externalId": "order-123456"
}