How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

XRPay Payouts API

The Payouts API from XRPay — 8 operation(s) for payouts.

XRPay Payouts API is one of 7 APIs that XRPay publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include Payouts. The published artifact set on APIs.io includes an OpenAPI specification and 6 JSON Schemas.

This API exposes 11 operations across 8 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 2026-08-30.

Requests are made against a single base URL, https://api.xrpay.it.

11 operations 8 paths 8 schemas 1 DELETE7 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2026-08-30
Base URL
https://api.xrpay.it
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

XRPay Payouts API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Secret API key or XRPay Connect access token.

Paths & Operations 11

Across 8 paths, the API surfaces 11 operations — 1 DELETE, 7 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Payouts 11
GET
/api/v1/balances
Retrieve consolidated payout balances
retrievePayoutBalances 1 param → 200401
GET
/api/v1/payout-capabilities
List payout corridors and aggregate limits
listPayoutCapabilities 3 params → 200
GET
/api/v1/payout-institutions
List canonical banks and Mobile Money operators
listPayoutInstitutions 3 params → 200
GET
/api/v1/payout-destinations
List masked payout destinations
listPayoutDestinations → 200
POST
/api/v1/payout-destinations
Create or reuse a payout destination
createPayoutDestination 1 param body → 201409
GET
/api/v1/payout-destinations/{id}
Retrieve a masked payout destination
retrievePayoutDestination 1 param → 200404
DELETE
/api/v1/payout-destinations/{id}
Deactivate a payout destination
deletePayoutDestination 2 params → 204409
POST
/api/v1/payout-quotes
Quote an exact-net or maximum-balance payout
createPayoutQuote body → 201409
GET
/api/v1/payouts
List aggregate merchant payouts
listPayouts → 200
POST
/api/v1/payouts
Atomically reserve and execute a quoted payout
createPayout 1 param body → 201200409
GET
/api/v1/payouts/{id}
Retrieve aggregate payout and opaque delivery parts
retrievePayout 1 param → 200404

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are PayoutQuote (17 properties), Payout (16 properties), PayoutDestination (10 properties), PayoutInstitution (9 properties). Each schema is shown below with its type and property counts.

PayoutDestination
object
10 properties 7 required
PayoutQuote
object
17 properties 12 required
PayoutInstitution
object
9 properties 9 required
MoneyString
string
An exact non-negative decimal amount. Never parse this as a binary floating-point number.
PayoutQuoteCreate
object
5 properties 3 required
Error
object
1 property 1 required
Payout
object
One merchant-facing payout. Delivery IDs are opaque and never identify a provider.
16 properties 12 required
PayoutDestinationCreate
object
5 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xrpay-payouts-api-openapi.yml Raw ↑

Other APIs XRPay publishes across the network.

XRPay Connected account API
XRPay Payment intents API
XRPay Payroll API
XRPay Refunds API
XRPay Sandbox API
XRPay Webhooks API
Where this information came from

This is an independent, third-party profile of XRPay Payouts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.