xpendB2B
Core concepts

Hosted checkout

Hosted checkout gives you a production-ready payment surface without building on-chain UX yourself.

What you configure

  • Storefront identity and publish state.
  • Allowed quote chains and fiat options.
  • Pricing/quote behavior and QR entry points.

Merchant checkout endpoints

GET/api/v1/merchant/checkout/storefrontsList storefronts
POST/api/v1/merchant/checkout/storefrontsCreate storefront
PUT/api/v1/merchant/checkout/storefronts/{storefrontId}Update storefront
POST/api/v1/merchant/checkout/storefronts/{storefrontId}/logoUpload logo
GET/api/v1/merchant/checkout/quote-chain-optionsAllowed quote chains
GET/api/v1/merchant/checkout/fiat-currency-optionsAvailable fiat currencies
GET/api/v1/merchant/checkout/pricing-configRead pricing config
PUT/api/v1/merchant/checkout/pricing-configUpdate pricing config
GET/api/v1/merchant/checkout/qrcodesList checkout QR codes
POST/api/v1/merchant/checkout/qrcodesCreate checkout QR code
PUT/api/v1/merchant/checkout/qrcodes/{qrCodeId}Update checkout QR code

Developer pattern

Most teams configure storefront/checkout via merchant endpoints, then create payment intents from backend order events.

Public browsing vs authenticated config

Storefront presentation is public-facing, but creation and management stay behind authenticated merchant APIs.

For implementation details, continue in /business/reference/checkout.

Ready to build?
Get an API key

Sandbox-only credentials, no card required.

Stuck on something?
Talk to a human

DevRel responds in office hours.

PreviousAssets & networksNextOverview