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 Payment intents API

The Payment intents API from XRPay — 5 operation(s) for payment intents.

XRPay Payment intents 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 Payment Intents. The published artifact set on APIs.io includes an OpenAPI specification and 6 JSON Schemas.

This API exposes 6 operations across 5 paths, and defines 9 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.

6 operations 5 paths 9 schemas 3 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 Payment intents 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 6

Across 5 paths, the API surfaces 6 operations — 3 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Payment Intents 6
GET
/api/v1/capabilities
List the authenticated merchant's ready payment methods and settlement…
retrieveAccountCapabilities → 200401
GET
/api/v1/payment-intents
List payment intents
listPaymentIntents 4 params → 200
POST
/api/v1/payment-intents
Create a payment intent
createPaymentIntent 1 param body → 201200400401409429
GET
/api/v1/payment-intents/{id}
Retrieve a payment intent
retrievePaymentIntent 1 param → 200404
POST
/api/v1/payment-intents/{id}/cancel
Cancel an unpaid payment intent
cancelPaymentIntent 1 param → 200409
POST
/api/v1/payment-intents/{id}/confirm
Submit a Mobile Money one-time code
confirmPaymentIntent 1 param body → 200400404409

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are PaymentIntent (31 properties), PaymentIntentCreate (19 properties), PaymentNextAction (8 properties), TestBalanceCredit (7 properties). Each schema is shown below with its type and property counts.

TestBalanceCredit
object
An idempotent credit to the connected business's isolated virtual payout balance. It never represents external money movement.
7 properties 7 required
Settlement
object
4 properties
LineItem
object
4 properties 1 required
PaymentNextAction
object
8 properties 1 required
MoneyString
string
An exact non-negative decimal amount. Never parse this as a binary floating-point number.
DirectMobileMoneyPaymentMethodData
object
2 properties 2 required
PaymentIntentCreate
object
19 properties 3 required
Error
object
1 property 1 required
PaymentIntent
object
31 properties 11 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xrpay-payment-intents-api-openapi.yml Raw ↑

Other APIs XRPay publishes across the network.

XRPay Connected account API
XRPay Payouts 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 Payment intents 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.