Payment links and HTML buttons.
Share a published checkout configuration without placing an API key in your website.
01Create a draft
Use Payment links in the dashboard. Enter a fixed testnet asset/network, positive decimal price, title, optional description, payment window of 5–1440 minutes, and optional checkout count limit. Set a verified return website only if needed. Price and asset cannot be edited after creation; create a new link to change them.
02Publish deliberately
Review the complete configuration, verify your passkey and confirm publication. The link freezes branding at first publication. Drafts are not publicly accessible. Pausing stops new checkouts; archiving is permanent. Existing orders keep their original payment window.
03Add a button to your website
Copy the exact HTML button from the published link dialog. It opens the hosted payment page with an ordinary accessible link and no credential. Each buyer starts checkout explicitly. Workspace capacity and any link-specific usage limit still apply.
04Handle an interrupted start
The hosted link keeps only a public request identifier and optional public checkout ID in session storage. Use Recover checkout request after a lost response. Recovering the same committed request still works after the merchant pauses the link. Starting a separate checkout is an explicit action.
<!-- Replace the URL with the published link copied from your dashboard. -->
<a href="https://app.allwallex.com/pay/PUBLISHED_PUBLIC_ID" target="_blank" rel="noopener noreferrer">Pay with crypto</a>
// App-session management endpoints, not bearer-key endpoints:
POST /v1/workspaces/{workspaceId}/merchant/payment-links
POST /v1/workspaces/{workspaceId}/merchant/payment-links/{id}/publish
{ "expectedRevision": 1 }
// Both writes require their own stable Idempotency-Key.Open your workspace