StatusSupportGet API keys
Funding

Check if iban is valid

POST/v1/teller/iban/validate

Checks whether an IBAN is well formed and its check digits are correct. It does not check that the account exists or who holds it.

Send iban (required) and countryCode (optional) in the JSON body. This operation does not accept query parameters. An invalid IBAN is not an error: the response is 200 with result: false.

Authorization

ApiKeyAuth
X-Api-Key<token>

For accessing these endpoints a valid API key must be sent in the X-Api-Key header.

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

Check if iban is valid
curl --request POST \  --url 'https://gateway.bit2me.com/v1/teller/iban/validate' \  --header 'Content-Type: application/json' \  --data '{  "countryCode": "ES",  "iban": "ES91 2100 0418 4502 0005 1332"}'
Example1 of 2
{  "result": false}

Accept a withdrawal draft POST

Confirms and submits a previously created withdrawal draft, creating the actual withdrawal order on the blockchain. The draft must belong to the authenticated user and must not have expired. Every acceptance requires a second-factor code in the `x-totp` header. The first request is usually sent without it and answered with `428`: * For stablecoin withdrawals, the `428` means a code has just been sent to the user, and its body says through which channel (`sfaType`) and which phone channels are available (`availableChannels`, `defaultChannel`). * For any other currency, the `428` only says that the code is needed. Then repeat the same request with the code in `x-totp` and the channel it came through in `x-totp-type`. A wrong code returns `420` and nothing is executed.

Execute an order POST

Executes an order previously created with `POST /v1/teller/order/proforma`, charging it with the payment method chosen there. A proforma can be executed only once and only while it is valid, so an expired one has to be created again. When the user has to complete the payment, for example to pass 3-D Secure on a card or to approve a Bizum payment, the response comes with `status: waiting-user` and `provider.requestConfiguration` says how: open its `uri` when `type` is `iframe`, or wait for the user to approve it outside the app when `type` is `external`.