🚧

Use under special circumstances ONLY

This endpoint is specific to customers with special circumstances that need to be able to register an end user with Sila that has already gone through the KYC process with a different provider, and therefore will not be going through Sila's KYC process.

If this is not you, use /register and go through the typical KYC flow outlined in our KYC overview documentation here.

This endpoint will NOT work unless the end user has already passed KYC with the provider.

This endpoint takes a provider token and provider name into the request and returns the user_handle for the registered entity. This entity will be created having already passed KYC, and will not need to go through Sila's KYC process.

You can then proceed with linking any necessary bank accounts and this end user can begin transacting.

Currently the only provider supported in this request is Plaid.

Request

Provider Tokens

Please note that using a new provider token will create a new entity. If you have already used a provider token to register a new entity, you will receive an error that that token is already associated to an entity.

Authorization / Authentication

Use a valid access token in an Authorization: Bearer request header.

See Authenticating with an Access Token for more details.

POST /0.2/register_with_provider_token HTTP/1.1
sandbox.silamoney.com
Content-Type: application/json
Authorization: Bearer [GENERATED JWT TOKEN HERE]

{
  "header": {
    "created": 1234567890, //required
    "app_handle": "<your app_handle>", //required
    "version": "0.2", 
    "reference": "<your unique id>"
  }, 
  "provider_token": "processor-xxx-xxx", //required
  "provider": "plaid" //required
}

***

HTTP/1.1 202 OK

{
  "success": True,
  "reference": "<reference_id>",
  "entity_handle": "<new_user_handle>" 
}

Request Attributes

Responses