xrpl-x402-client
Client mechanism for x402 v2 exact XRPL payments.
from x402 import x402Client
from xrpl_x402_client import register_exact_xrpl_client
client = register_exact_xrpl_client(x402Client(), signer)
client.set_spend_controls({"max_amount_per_payment": "$1"})
ExactXRPLClientScheme constructs and signs sequence or ticket payments,
derives LastLedgerSequence from the timeout, binds custom networks through
NetworkID, hashes advertised invoice IDs, and emits only
{"signedTxBlob": "..."} as the scheme payload.
Use XRPLAssetSpendLimit for XRP, USDC, or custom IOUs. These assets are not
silently authorized by the default pegged-asset policy.
The XRPLPaymentTransport and wrap_httpx_with_xrpl_payment helpers use the
official x402AsyncTransport, which retries a replayable protected request at
most once.
Custom async streaming bodies are sent exactly once and a 402 is returned to
the caller without buffering, signing, or automatic retry.
1 maintainer
Metadata
1 maintainer
Release files for xrpl-x402-client 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| xrpl_x402_client-0.2.0.tar.gz | 8.6 kB | With provenance | Details for xrpl_x402_client-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| xrpl_x402_client-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for xrpl_x402_client-0.2.0-py3-none-any.whl |
Total release size: 19.2 kB
Release files / xrpl_x402_client-0.2.0.tar.gz
| Download URL | xrpl_x402_client-0.2.0.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
efae0f10d73156fde70befc899997755e553382708f5f9e76f0efa533406b493
|
|
BLAKE2b-256 checksum How to use checksums |
57e9d4e5860c9c159ce988b4f0dea95869b7e42d092ac39a811f02030dc41a8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logRelease files / xrpl_x402_client-0.2.0-py3-none-any.whl
| Download URL | xrpl_x402_client-0.2.0-py3-none-any.whl |
|---|---|
| Size | 10.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7ba6b8ac4efb4b30df362a91ee5f1f83b210d873f7507c400f7788a1f5c076e3
|
|
BLAKE2b-256 checksum How to use checksums |
ca0d4309cfbe3011f84facc26531d16b2f615dff5f608ded57963ce6e9a24435
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logSecurity for xrpl-x402-client 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for xrpl_x402_client-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 3, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
