API access.
No charge.

Direct REST API and signed webhooks are included with every ePayVista account. Log in, reveal your key, build against the free sandbox, go live. You pay the same flat 1% per transaction as everyone else and nothing for the access itself.

Get your API keyOpen the sandbox

Beta programme, September 2026. Onboarding other people's merchants under your own brand is a different product. That is White-Label.

How do I integrate ePayVista?

Every ePayVista account includes a free REST API (currently in beta) with an API-Key header and signed webhooks, so any custom checkout can create a payment and be told the moment it settles. It also works for checkout on Shopify and Wix stores: on Wix it shows as a payment option inside the Wix checkout, and on Shopify the buyer pays by link straight after placing the order. WooCommerce stores install the free plugin instead and are live in about five minutes, and a paid white-label option exists for anyone onboarding merchants under their own brand. Test against the free sandbox first, then reveal your live key in the merchant portal under Developer.

How to get your key. About two minutes.

  1. Create an account or log in to the merchant portal at pay.epayvista.com/portal. It is the same login you use for payment links.
  2. Open Developer in the portal's top nav. Your API key and callback secret are there, revealed with your password.
  3. Set your webhook callback URL on the same page. Signed with X-EPV-Signature, HMAC-SHA256 over the raw body.
  4. Build against the sandbox first: free credentials, test tokens on demand, no live funds.

Everything else is documented. Every endpoint, every field, every error code, the full payment lifecycle and the signed-webhook contract, with working verification snippets in Node, Python and PHP. You should not need to email us to finish an integration.

Full API reference →

Selling through the WooCommerce plugin already? Your store keeps its own connection and its own payout wallet, and your orders keep showing in WooCommerce. A portal login is a separate Payment Links account with its own key, secret and payout wallet - register above and it will not list your store's orders. If you want the two joined to one account, tell us and we will link them.

What you get.

  • POST /api/v1/payment creates a payment session and returns a hosted checkout URL and a reference id.
  • GET /api/v1/payment/reference/:ref reads status, amount, chain, confirmations and the settlement transaction.
  • Signed webhooks on payment, settlement and account status, with a retry schedule on your side's failures.
  • Card, Apple Pay, Google Pay and wallet at checkout for your customer. USDC or USDT to your wallet for you, on-chain, usually within seconds.
  • Standard 1% per transaction. No monthly fee, no setup fee, no volume minimum.

Checkout on Shopify and Wix.

Both work through the API today. There is no app to install from us; the integration is a small piece of code on your side, written once. Your developer can build it from the API reference, or we build it for you with the $500 API integration below.

  • Wix: ePayVista inside the Wix checkout. Wix lets a site owner add their own payment provider with the Velo Payment Provider service plugin. Your plugin creates the payment with POST /api/v1/payment, passing the order total and Wix's return and cancel addresses, and sends the buyer to the checkout URL we return. When the payment settles, our signed webhook calls an HTTP function on your Wix site, which marks the Wix transaction approved and the order paid. Needs Velo (Dev Mode) and a Wix plan that accepts online payments.
  • Shopify: pay by link right after the order is placed. Shopify only allows payment providers it has approved inside its own checkout page, so the buyer completes the order first and pays a moment later. Add ePayVista as a manual payment method, have your server create the payment from Shopify's order-created webhook and send the buyer the checkout link, then mark the order paid through Shopify's Admin API when our webhook arrives. The order shows as payment pending only until the buyer pays.

Same flat 1%, same instant USDC payout to your wallet, same order minimums as below.

You may not even need it.

These create real payments and settle on-chain exactly like the API does, with no code:

Want it built for you?

Optional. The access is free; our time is not.

  • Plugin or payment-link setup: $250. We install and configure it on your store and put a test order through with you. Pay by card or in crypto.
  • API integration: $500. We build the integration against your backend. Pay by card or in crypto.

Live limits to design around.

These are engine floors, not per-account settings. Know them before you build, because they decide whether your catalogue works:

  • $5 minimum order. Anything below $5 is rejected outright. No link is created.
  • $20 minimum for the card and wallets tile, because it settles on Ethereum. The Stripe card option (card, Apple Pay, Google Pay) starts at $5.
  • $20 minimum on Ethereum, because L1 gas would otherwise swallow the fee. Base and Polygon start at $5.
  • You pay the on-chain sweep gas. Small orders are uneconomic for you as well as blocked, so bundle them or route them elsewhere.

Everything at $20 and up gets the full set of rails. GET /api/rails returns the current per-rail minOrderUsd and needs no key - treat it as the source of truth. The sandbox enforces none of these, on purpose.

Onboarding other people's merchants under your own brand, with your own pricing on top of our 1%, is a different product. That is White-Label, and it is the part that costs money.