Retrieve Payout Beneficiary
Retrieves a single payout beneficiary by ID. Returns 404 if the beneficiary does not exist or is not owned by the caller.
Authentication
AuthorizationBearer
OAuth 2.0 access token issued by the CrissCross authorisation server.
Path parameters
payoutBeneficiaryId
UUID of the payout beneficiary.
Response
Payout beneficiary retrieved successfully.
payoutBeneficiaryId
UUID of the beneficiary.
merchantId
Merchant ID that owns this beneficiary.
merchantReference
Merchant-provided reference for de-duplication and lookup. Persisted on create and round-trips on every read.
status
Lifecycle status of a payout beneficiary.
pending_review— created, awaiting account verification and AML pre-screening, or held for review. A name-mismatch hold (the receiving network returned a different account holder name) is cleared by the merchant via the signal endpoint (accept/reject). An AML compliance hold is cleared by CrissCross’s compliance team in our screening provider’s tooling — the merchant cannotaccept/rejectit.approved— account verification and AML pre-screening both passed; can be referenced frompayoutBeneficiaryIdon a payout.rejected— declined by signal, by AML pre-screening, or after exhausting verification retries. Terminal.failed— verification or screening errored in a non-recoverable way. Usesignal: retryto re-run the checks.
recipient
Recipient (payee) details. The type discriminator determines which fields are present.
verifications
Outcome of the account-verification + AML pre-screening passes run against the beneficiary.
createdAt
ISO-8601 timestamp the beneficiary was created.
updatedAt
ISO-8601 timestamp of the last update.
attributes
Free-form key/value metadata attached to the beneficiary at create time.
Errors
401
Unauthorized Error
403
Forbidden Error
404
Not Found Error
500
Internal Server Error