AURA · MERCHANT CHECKOUT · COMING NEXT

Aura Pay Checkout

Planned merchant checkout: customers would pay with supported testnet assets while a future business flow routes money through a Private Balance. This page is a preview; it does not send payments.

PLANNED CUSTOMER CHECKOUTPLANNED AURA PRIVATE BALANCEMERCHANT BALANCE (ROADMAP)

MERCHANT CHECKOUT SPECIFICATION

Preview What Your Customers Would See

COMING NEXT

Roadmap Preview: Aura Pay Checkout is scheduled for future release. The preview below illustrates the intended merchant flow.

Merchant checkout

Private Balance routing

Embedded payment UI

Nothing on this page sends money. It is a product preview.Learn More →

Separate Business Reserves

Public payment patterns can reveal or help infer operational balances and sales activity. Aura's planned model would separate business reserves from individual payment transactions.

Planned Multi-Chain Checkout

The planned flow supports checkout across selected testnet networks. No merchant payment or settlement is executed here.

Planned Embed Model

The snippet below is an illustrative integration shape, not a live SDK. Merchant APIs and payment routing remain roadmap work.

DEVELOPER INTEGRATION

Example Embed Shape

Illustrative code only · no live SDK is published

<!-- Prototype Preview — not executable -->
<!-- Aura Pay Checkout integration is planned for a future release. -->
<!-- No public SDK script or copy-paste button is available yet. -->

Standard Crypto Merchant vs. Aura Pay Checkout

Standard Crypto Gateway

May expose a payment address and its public history.
Timing and amounts can reveal or help infer activity.
A buyer does not automatically receive proof of total reserves.
Requires custodying multiple volatile tokens.

Planned Aura Pay Checkout

Goal: create a single-use payment request for each invoice.
Goal: reduce direct exposure of merchant wallet history.
On-chain metadata may still allow transaction correlation.
Merchant custody and settlement are not implemented yet.