Machine Payments with XRPay
Create an XRP or RLUSD payment requirement, verify the submitted XRPL transaction, and record paid API usage.
What the Current API Does
A protected service can return a payment requirement containing the amount, asset, destination, resource, expiration, and nonce. After the client submits an XRPL payment, the service sends the transaction hash and requirement to XRPay for verification.
Features
Payment Requirement
Create a time-limited XRP or RLUSD requirement for a specific resource and merchant destination.
On-Ledger Verification
Check the submitted transaction hash against the required destination, asset, amount, nonce, and expiration.
Client-Signed Payment
The paying client signs through its own compatible XRPL wallet or key-management system.
Direct XRPL Confirmation
Direct XRP and supported XRPL-token payments typically confirm in 3–5 seconds.
Get Started
Review the current endpoint format and test the full requirement, payment, verification, and resource-delivery flow before using it in production.