Get payment method details

Returns the full account details behind one payment method.

GET

GET/recipients/{orgId}/{recipientId}/methods/{methodId}/details

curl -s "$AVVIO_BASE_URL/recipients/$AVVIO_ORG_ID/$recipientId/methods/$methodId/details" \
  -H "x-api-key: $AVVIO_API_KEY"

const recipientId = '<recipientId>';
const methodId = '<methodId>';

const res = await fetch(`${process.env.AVVIO_BASE_URL}/recipients/${process.env.AVVIO_ORG_ID}/${recipientId}/methods/${methodId}/details`, {
  headers: {
    'x-api-key': process.env.AVVIO_API_KEY,
  },
});
console.log(res.status, await res.json());

import os
import requests

recipientId = "<recipientId>"
methodId = "<methodId>"

res = requests.get(
    f"{os.environ['AVVIO_BASE_URL']}/recipients/{os.environ['AVVIO_ORG_ID']}/{recipientId}/methods/{methodId}/details",
    headers={
        "x-api-key": os.environ["AVVIO_API_KEY"],
    },
)
print(res.status_code, res.json())

200OK

{
  "id": "cmf3k2xa10005q8b7w9x2y3za",
  "kind": "fiat",
  "currency": "MXN",
  "address": null,
  "details": {
    "clabeNumber": "012180000080004471"
  }
}

{
  "type": "UNAUTHORIZED",
  "status": 401,
  "detail": "Invalid API key",
  "resolution": "Check the API key was copied whole and has not been revoked.",
  "requestId": "req-9bz",
  "message": "Invalid API key",
  "statusCode": 401
}

{
  "type": "FORBIDDEN",
  "status": 403,
  "detail": "This API key cannot access that organization",
  "resolution": "This key is scoped to a different organization.",
  "requestId": "req-9d0",
  "message": "This API key cannot access that organization",
  "statusCode": 403
}

{
  "type": "RATE_LIMITED",
  "status": 429,
  "detail": "ThrottlerException: Too Many Requests",
  "resolution": "Back off and retry after the Retry-After interval.",
  "requestId": "req-9e1",
  "message": "ThrottlerException: Too Many Requests",
  "statusCode": 429
}

Path parameters

orgIdstringRequired
The opaque organization id issued to you, normally CUID-shaped (for example cmsx…). It is not an org_-prefixed alias. Pass it unchanged in every organization-scoped path.
recipientIdstringRequired
Opaque recipient id returned by this API. Pass it unchanged.
methodIdstringRequired
From the recipient's paymentMethods[].id.

Behavior

Lists carry only last4. This returns what was actually registered, which is useful for showing a user the account on file before they authorize a payout, and for confirming what you stored matches what we hold.

Fetch it on demand for one method. List payloads leave it out so bulk reads do not move full account numbers around. A read-only key is refused this read (403 INSUFFICIENT_SCOPE); lists carry last4, which is what reconciliation needs.

Responses

200The registered account details

Body

idstringRequired
kindstringRequired
Allowed values:fiatcrypto
currencystring | nullRequired
addressstring | nullRequired
Crypto methods only. The destination wallet address.
detailsobject | nullRequired
The corridor fields as registered, keyed by the field ids GET /corridors published (for example clabeNumber). Null on a crypto method, and on a method saved before we kept the full details.

Errors

401
The key was refused. Nothing ran.
- UNAUTHORIZED: missing, invalid or revoked, or a key on a route that does not accept one.
- KEY_EXPIRED: the key passed the expiry it was issued with. Issue a new one; an expired key cannot be rotated.
- KEY_IP_NOT_ALLOWED: the key is pinned to source addresses and this request came from another.
403
FORBIDDEN (a key for a different organization), ACCOUNT_BLOCKED (API access suspended), or INSUFFICIENT_SCOPE (a read-only key: full account details need the write scope).
404
Unknown recipient or method
429
Too many requests. The default ceiling is 100 requests per minute per API credential on a 60-second window. High-volume payout and reconciliation routes declare a 600/minute override, and batch submission a 30/minute ceiling. A separate 2,000/minute per-source-IP abuse ceiling always applies.

Obey Retry-After; it is in seconds and is authoritative. A 429 means the request was refused before the handler ran. Retry reads normally; retry an idempotent mutation with its same Idempotency-Key.

Error body · Error

typestringRequired
Stable machine-readable code.
detailstringRequired
What went wrong, in a sentence. Always a string, so detail.toLowerCase() is safe.
More
This is the field to read on BAD_REQUEST and PROVIDER_REJECTED, where the type alone does not name the condition.
messagestringRequired
The same text as detail, kept for integrations written before detail existed. Read detail.
resolutionstringOptional
What to do about it, when there is a specific answer. It is not on every error (it is absent on BAD_REQUEST, NOT_FOUND, PAYOUT_NOT_CANCELABLE and DESTINATION_ACCOUNT_NOT_FOUND), so treat it as optional and fall back to detail.
statusintegerRequired
HTTP status, repeated in the body.
statusCodeintegerRequired
The same value as status, kept for integrations written before status existed. Read status.
requestIdstringRequired
Quote this to support and we can find the exact request. Also sent as the x-request-id response header, which is the only place it appears on a successful response. Success bodies do not carry it. Send your own x-request-id on the request and we use it, so your trace and ours share one identifier; otherwise we mint one.
errorsarray of stringOptional
Present on VALIDATION_ERROR; names each field that failed.
originalIdempotencyKeystringOptional
On DUPLICATE_REQUEST_DETECTED only. Send the request again with this to receive the original payout instead of making a second one. Without it there is no way to recover except by risking a double payment.
originalPayoutIdstringOptional
On DUPLICATE_REQUEST_DETECTED only. The payout the first request created.
originalBatchIdstringOptional
On a batch DUPLICATE_REQUEST_DETECTED. The run the first request created.
originalRequestIdstringOptional
On a 409 PAYOUT_OUTCOME_UNKNOWN replay. The requestId of the call whose outcome is unknown; quote it to support.
existingRecipientIdstringOptional
On BANK_ACCOUNT_ALREADY_LINKED. The recipient in your organization that already holds this account.
existingMethodIdstringOptional
On BANK_ACCOUNT_ALREADY_LINKED. The payment method on that recipient.

Branch on type, never on the status or the message. Every error type is listed with what to do about it.

Avvio Partner Payouts · Recipients · operation getBeneficiaryMethodDetails

Try it: Get payment method details

GET https://api.avvio.xyz/business/api/v1/recipients/{orgId}/{recipientId}/methods/{methodId}/details

API key Required

Test keys only. Sent as x-api-key through this site's proxy to the Avvio API, never saved, and cleared when you close this dialog.

orgId pathRequired

recipientId pathRequired

methodId pathRequired

Was this page helpful?