Upload a Sender file

Uploads one KYC document or order-level proof-of-transfer document. Returns a file_id to reference from a later KYC submission or order.

A file is always scoped to the Sender it was uploaded against — it can’t be referenced by a KYC submission or order for a different Sender.

POST /api/v2/payouts/senders/{id}/files

Upload a Sender file

cURL

curl --request POST \
  --url https://api.mansa.xyz/api/v2/payouts/senders/{id}/files \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: multipart/form-data' \
  --header 'x-api-key: <api-key>' \
  --form file='@example-file' \
  --form 'fileType=<string>'

201

{
  "file_id": "1218543853301276650/KYC_ID_CARD_FRONT/2024-10-17/1729145682729329.jpeg"
}

Authorizations

x-api-key · string · header · required

API key for authentication

Authorization · string · header · required

ES256 JWT signed by the private key registered to the API key above. Claims: sub (=API key), uri, nbf, iat, exp, and bodyHash (HMAC-SHA512 of uri + rawBody + nbf using a shared secret, base64).

Path Parameters

id · string<uuid> · required

ID of the Sender

Body

multipart/form-data

file · file · required

Max 50MB.

fileType · string · required

Opaque partner file-type code (e.g. a passport photo page vs. a business registration certificate) — treat as an opaque required string, not an enum.

Response

201

application/json

File uploaded

file_id · string · required

Opaque partner-issued id — store verbatim, pass back exactly as received.

Example:

"1218543853301276650/KYC_ID_CARD_FRONT/2024-10-17/1729145682729329.jpeg"