Buyer-session: record the tos_id from the ToS-acceptance redirect. - Caratuva

Buyer-session: record the tos_id from the ToS-acceptance redirect.

curl --request POST \
  --url https://api.example.com/v1/public/buyer-kyc/tos-accepted \
  --header 'Content-Type: application/json' \
  --data '{}'

POST

/

v1

/

public

/

buyer-kyc

/

tos-accepted

Buyer-session: record the tos_id from the ToS-acceptance redirect.

curl --request POST \
  --url https://api.example.com/v1/public/buyer-kyc/tos-accepted \
  --header 'Content-Type: application/json' \
  --data '{}'

Body

application/json

The body is of type object.

Response

200

ToS acceptance recorded

Buyer-session: mint a settlement-partner ToS-acceptance URL. Buyer-portal directs the buyer to the returned URL; on acceptance the settlement partner redirects to ?tos_id=... which the buyer-portal forwards via /tos-accepted below.Buyer-session: mint a signed PUT URL for a KYC file (selfie or ID document). The buyer-portal PUTs the file to uploadUrl with uploadHeaders, then sends publicUrl in the /buyer-kyc submit.