Get beneficiary requirements
Returns what a beneficiary on one corridor must contain: its fields, the rules each value must meet, and the documents it may carry. Build your form, or map your stored data, from this response, then send the values to Create beneficiary under the same field names.
The answer is the same whether the beneficiary is for you or for one of your customers, because your customers are offered your corridors. It can change when Ryno changes how a corridor is paid, so read it before you create a beneficiary rather than caching it for long.
Query
corridorIduuidqueryrequiredA corridorId from List payout corridors.
Response
corridorIduuidThe corridor you asked about.
destinationCountrystringThe beneficiary's country, ISO 3166-1 alpha-3, for example CHN.
currencystringThe currency the beneficiary receives, for example USD.
railstringHow the beneficiary is paid on this corridor, for example RTGS. Informational; you never send it.
fieldsobject[]The fields a beneficiary on this corridor can have, in the order to show them. Send each value in details on Create beneficiary, keyed by name. A field that is not in this list is refused.
documentsobjectThe supporting documents a beneficiary on this corridor may carry. Documents are optional.
These rules let you check values before you send them. Ryno checks them again on Create beneficiary and names the first field that fails.
Errors
| Code | HTTP | Meaning |
|---|---|---|
BeneficiaryRequirement.InvalidRequest | 400 | corridorId is missing. |
Request.Invalid | 400 | corridorId is not a uuid. |
Auth.Unauthorized | 401 | The token is missing or invalid. |
Auth.Forbidden | 403 | The token is not a partner credential, or lacks partner.read. |
BeneficiaryRequirement.CustomerInactive | 403 | Your account is not active. Contact support. |
BeneficiaryRequirement.CustomerNotFound | 404 | Your account could not be found. Contact support. |
BeneficiaryRequirement.CorridorNotFound | 404 | The corridor is not one you are offered. Use an id from List payout corridors. |
BeneficiaryRequirement.NotAvailable | 422 | The corridor cannot take beneficiaries yet. Do not retry unchanged; contact support if you need it. |
BeneficiaryRequirement.Unavailable | 503 | Requirements cannot be read right now. Retry with backoff. |
The 401, 429 and 503 responses from the API gateway use a different body. See Errors.