Interoperable asset payments

ONE PAYMENT API
FOR ASSETS
ACROSS CHAINS

Blockchain assets are fragmented. Developers shouldn't have to integrate every ecosystem individually just to accept payment. PayFlux normalizes payment, verification and settlement behind one interface — the merchant thinks in $50, not 73.21 XRP.

Try the demo storeRead the docs
XRPL

Source chain

FDC

Verification

FAssets

Settlement

Coston2

Record of truth

checkout.tspayflux-sdk
import { PayFlux } from "payflux-sdk"

const payflux = new PayFlux({
  apiKey: process.env.PAYFLUX_SECRET_KEY,
});

const payment = await payflux.payments.create({
  amount: "50.00",
  currency: "USD",
  acceptedAssets: ["XRP", "FXRP", "C2FLR"],
  settlementAsset: "FXRP",
});

No XRPL SDK. No FDC client. No FAssets lot arithmetic. No transaction watcher. The merchant integrates PayFlux — adding a chain later means adding an adapter, not rewriting the payment engine.

The lifecycle

A PAYMENT THAT CROSSES ECOSYSTEMS,
AND PROVES IT

Each stage produces something a third party can check. That is the difference between a payment gateway and an interoperability layer.

  1. 01XRPL Testnet

    Customer pays

    The customer sends testXRP with a memo that binds the transfer to the payment intent. For FXRP settlement they pay the FAssets agent directly, so the payment itself backs the mint.

  2. 02Flare Data Connector

    Flare verifies

    PayFlux requests a Payment attestation for testXRP. Flare's attestation providers vote, and a Merkle proof is published.

  3. 03PaymentRegistry

    Coston2 records

    The proof is submitted on-chain. The contract re-verifies it against FdcVerification — it never takes our word for it.

  4. 04FAssets · FXRP

    Merchant settles

    The attested payment executes an FAssets mint, and FXRP lands in the merchant's wallet. A real balance change, with a hash.

Asset registry

SUPPORTED MEANS
IMPLEMENTED

An asset appears as supported only when the whole path exists — watcher, verification and settlement. The router then answers a second, separate question on every checkout: is it available right now?

  • Prices come from FTSOv2 feeds read on Coston2
  • FAssets capacity is checked live, per payment
  • No route is offered that PayFlux cannot execute

  • XRP

    XRPL Testnet

    Verified through an FDC Payment attestation. The flagship cross-ecosystem path.

    Payment

  • FXRP

    Flare Coston2

    The FAssets representation of XRP. PayFlux's default settlement asset.

    Payment · Settlement

  • C2FLR

    Flare Coston2

    Native Coston2 payments. Final on arrival, so no external attestation is needed.

    Payment · Settlement

  • BTC · DOGE

    Bitcoin · Dogecoin Testnet

    FDC attests these chains, but PayFlux has no watcher or settlement path for them yet — so they are listed as unsupported.

    Not supported

The abstraction

Source asset and source chain go in. A verified payment comes out, in the settlement asset the merchant asked for.

The API stays constant while the chains underneath change. That is the whole proposition — and the reason PayFlux refuses to list an asset it cannot actually move, or claim a verification it cannot actually prove.

See it end to endCheck what's live
  Source asset
  Source chain
        │
        ▼
     PayFlux
        │
        ▼
  Verified payment
        │
        ▼
  Settlement asset
  Settlement chain