GET
/
api
/
v1
/
end-users
/
{end_user_id}
/
beneficiary-fiat-accounts
curl --request GET \
  --url https://sandbox-b2b.ripio.com/api/v1/end-users/{end_user_id}/beneficiary-fiat-accounts/ \
  --header 'Authorization: Bearer <token>'
[
  {
    "beneficiary_fiat_account_id": "123e4567-e89b-12d3-a456-4bedc4266abc",
    "created_at": "2019-08-24T14:15:22Z",
    "currency": "ARS",
    "account_fields": {
      "alias_or_cvu_destination": "0000465160000000013330"
    },
    "status": "ENABLED",
    "payment_method_type": "bank_transfer"
  },
  {
    "beneficiary_fiat_account_id": "4567e123-e89b-12d3-a456-4bedc4266abc",
    "created_at": "2020-08-24T14:15:22Z",
    "currency": "ARS",
    "account_fields": {
      "alias_or_cvu_destination": "0000465160000000013331"
    },
    "status": "DISABLED",
    "payment_method_type": "bank_transfer"
  }
]

Authorizations

​
Authorization
string
header
required

B2B’s White Label API uses OAuth2. Currently there is only one supported authentication flow:

  • clientCredentials allows you to access your own B2B account (First-Party Integration) and performs transactions against the public API. This oauth2 flow is well suited for this API, as it allows machine-to-machine communication.

Every call to the API has to be authenticated with an OAuth2 Token. In order to request this token, you will need to have sandbox or production API Keys (client id and client secret) that will be needed to generate a credential in order to negotiate an ephemeral access token.

Every request must be accompianed by an Authorization header with a value that follows the following schema: Bearer ACCESS_TOKEN

Path Parameters

​
end_user_id
string
required

End user's external ref, usually a uuid.

Query Parameters

​
status
enum<string>

Filters results based on its statuses

Available options:
DISABLED,
PROCESSING,
ENABLED,
SUSPENDED
Example:

"processing"

​
payment_method_type
string

Filters results based on its payment method type

Example:

"bank_transfer"

Response

200 - application/json
​
beneficiary_fiat_account_id
string

UUID4 formated unique id.

Example:

"123e4567-e89b-12d3-a456-4bedc4266abc"

​
created_at
string

ISO DateTime indicating creation date of Beneficiary Fiat Account

Example:

"2019-08-24T14:15:22Z"

​
currency
string

It defines the currency that the Beneficiary Fiat Account accepts.

Required string length: 3
Example:

"ARS"

​
account_fields
object

JSON fields with account identification details. It varies based on the account type. Example:

{“alias_or_cvu_destination”: “0000465160000000013330”}
​
status
enum<string>

Indicates Beneficiary Fiat Account status. Expected values: DISABLED, PROCESSING, ENABLED, SUSPENDED

Available options:
DISABLED,
PROCESSING,
ENABLED,
SUSPENDED
​
payment_method_type
string

Indicates the payment method type. Usually, bank_transfer.