Questions, answered.

Yes, and it is free. Direct REST API and signed webhooks are included with every ePayVista account. Log in at pay.epayvista.com/portal, open Developer, and reveal your key with your password. Details on the API access page.

No. As of September 2026 API access is part of the standard account under a beta programme. You pay the same flat 1% per transaction as every other merchant and nothing for the access. The only paid items are optional done-for-you integration work ($250 or $500) and the White-Label platform.

On the sandbox page: endpoints, the API-Key header, request and response shapes, and the webhook signature scheme, plus free sandbox credentials and test tokens so you can run the whole flow before you touch live funds. Your live key is in the portal under Developer.

Yes, and it is free - you do not need to buy anything to use it. It runs the real API on a test network, so you can create a payment session, register a callback and receive a signed webhook before you spend a dollar. It cannot take live payments. Get credentials at pay.epayvista.com/sandbox.

Your live API key and callback secret in the portal, a form to set your webhook URL, HMAC-signed webhooks for payment, settlement and account status, and the free sandbox to build against. Same 1% rate.

Yes, optionally: $500 for a done-for-you API integration against your backend, or $250 if you only need the plugin or payment links set up and tested. The access itself is free either way.

No. Using the API for your own store is free. Being your own payment processor, onboarding other merchants under your brand and charging them your own fee on top of our 1%, is the White-Label platform, and that is paid: $1,000 Pilot, then $5,000 setup for the hosted tier.

It handles everything for you, so you never touch an API key. Install it, paste your payout wallet address and you are live. That is the point of it.

1% per transaction. No monthly fee, no setup fee, no rolling reserve, no volume minimum. API access is included. The only paid extras are optional integration help ($250 or $500) and the White-Label tiers.

As the payment confirms. There is no payout schedule, no 2 to 7 day wait and no weekly batch. Funds arrive as USDC or USDT in the wallet you control, usually seconds after checkout.

Straight to the payout wallet address you set. Funds are never held by us and never sit in an account we control, so there is nothing to freeze and nothing to release. Every settlement has an on-chain transaction hash you can verify yourself.

The customer pays in ordinary money, the gateway converts it and pushes it on-chain to your wallet. On-chain transactions are final, so there is no mechanism for the customer's bank to claw the payment back from you.

Yes, and it matters if you sell cheap items. $5 is the hard floor and orders below it are rejected outright. The card and wallets tile needs $20, because it settles on Ethereum; the Stripe card option starts at $5. Ethereum needs $20 because of L1 gas; Base and Polygon start at $5. GET /api/rails returns the current minOrderUsd for every rail and needs no key. You also pay the on-chain sweep gas, so very small orders are uneconomic as well as blocked. Everything at $20 and up gets every rail.

If they are short by 5% or less, the order still completes and you keep what arrived. If they are short by more than 5%, the funds are still forwarded to your wallet but the order is not marked complete, and you get an email so you can decide what to do. Nothing is ever held back.

USDC on Base, Polygon or Ethereum; Polygon also takes USDT and Ethereum also takes PYUSD. Which one you receive follows the option the customer used: Pay by card and Pay with Coinbase settle as USDC on Base, Card & wallets as USDC on Ethereum, and a customer paying from a crypto wallet picks the network and coin at checkout. Base and Polygon orders start at $5, Ethereum at $20 because of its network fee. The same wallet address receives on all three networks.

Every payment settles straight to your own wallet, so a refund is sent by you, from that wallet or by any other means you agree with the customer. There is no refund button in the portal or the API, and because a blockchain transfer is final the money cannot be pushed back to the customer's card from our side. The other side of that coin: nobody can pull a payment back from you either. There are no chargebacks.

Yes, under Settings in the portal or in the plugin settings on your store. Every change sends a notice to the email address on the account, so you will know if someone else did it. Payments already in progress keep the wallet that was on file when they were created; new payments use the new one. We never redirect a payment to a different wallet on request, including from the account holder, because a blockchain transfer is final the moment it is sent. Double-check the address before you save it.

No, it is the same for every store. A customer who pays within 5% of the total has almost always lost the difference to an exchange withdrawal fee or a network fee, and marking that order unpaid costs you the sale. The order note on the WooCommerce order shows the amount that actually arrived, and the 1% fee is taken from that amount before it reaches your wallet.

Three. You enable them per store under WooCommerce > Settings > Payments, or pick them per payment link in the portal. Pay by card (Stripe): credit or debit card, Apple Pay and Google Pay, orders from $5, for customers in the United States, settles as USDC on Base. Pay with Coinbase: card, Apple Pay, bank transfer or a Coinbase balance, orders from $5, aimed at US customers, settles as USDC on Base. Card & wallets: several licensed card providers, works for customers outside the United States as well, orders from $20, settles as USDC on Ethereum. Whichever the customer picks, you receive the amount minus 1% and the network fee.

Pay by card: no account. Stripe runs its own checks on first-time buyers, which for some US customers include date of birth and Social Security number, and does not ask again once a customer is verified. Pay with Coinbase: a customer with a Coinbase account signs in; in the United States Coinbase also offers a guest checkout with a debit card or Apple Pay, within limits that Coinbase sets, and Coinbase decides which of the two a customer is shown. Card & wallets: each provider sets its own identity check for first-time buyers and shows it on its own page before any card details are entered. Customers paying directly from a crypto wallet need no account and no verification at all.

The card providers run their own 3-D Secure and fraud checks on every card payment. That cannot be switched on or off per store or through the API, and there is no non-3DS route. Per-transaction card limits are set by each provider too and can depend on the customer's card and country; we add no limits of our own and there is no merchant underwriting.

The descriptor of the card provider that processed the payment, charged in US dollars. It does not show your store name or ours. An order priced in another currency is converted to dollars at the live rate when the payment is created, and the checkout tells the customer so before they pay.

Yes, with nothing to switch on. The plugin converts the order total to US dollars at the live rate when the payment is created, and you receive the equivalent in USDC. For customers outside the United States enable Card & wallets rather than Pay by card (Stripe), which serves US customers only. A quick test order from your customers' country with your own card is the best way to confirm it works for them.

WordPress and WooCommerce is live and listed on the WordPress.org plugin directory. Any other platform works today through hosted payment links, and AI agents through the MCP endpoint. Shopify and Wix stores can take checkout through the free REST API: on Wix as a payment option inside the Wix checkout, on Shopify as a pay-by-link step right after the order is placed.

About five minutes for the plugin: upload the zip, paste your payout wallet address, done. Payment links take less.

No. If you can upload a file to WordPress and copy a wallet address, that is the full skill requirement.

No. There is no application queue, no underwriting file and no documents to submit for the account itself. Verification happens on the paying customer at checkout, not on you.

No. They pay by card, Apple Pay or Google Pay depending on their region and never see a wallet or a coin. Crypto is only how you get settled.

ePayVista is built mainly for US merchants selling to US customers, and that is where card payments work best. Merchants and customers in other countries can use it, but card payments outside the US are not guaranteed. Card payments are handled by licensed third-party card providers, and each provider decides which countries, cards and amounts it accepts and what checks the customer must complete (such as 3D Secure or ID verification). ePayVista does not control those decisions. If you sell outside the US, run a real test payment from your customers' country before you go live. Customers paying directly in crypto can pay from anywhere.

Once. The first time a customer pays by card, the card provider checks who they are, the same as any card purchase of digital dollars. It is a one-time step with that provider, so repeat orders go straight through. US customers paying with the Stripe option may be asked for date of birth and SSN. Turn on Card & Wallets as well: it offers other card providers with their own checks, so a customer who would rather not use Stripe has a second route. Customers who already hold USDC or USDT can pay from their wallet with no verification at all. You, the merchant, are never asked for KYC.

No. The plugin runs live from the moment it is connected, so the way to test is a real small order on your own store: $5 or more for Pay by card and Pay with Coinbase, $20 or more for Card & wallets (it settles on Ethereum). Pay it as a customer would. When the payment confirms, the order moves to Processing and the money lands in your payout wallet minus the 1% fee and the network fee, so a test costs you only those fees. The free sandbox is for API integrations, not for the plugin.

When you press Connect, we call your site at /wp-json/epayvista/v1 to confirm the plugin is there and active. The usual reasons that fails: the plugin is installed but not activated; the site asks for a password or shows a browser check before every page, including /wp-json/; a security plugin blocks the WordPress REST API for visitors; or the domain is not pointed at your WordPress install yet, so a hosting placeholder page answers instead. Fix the one that applies and press Connect again. You can check it yourself: open https://your-store.com/wp-json/epayvista/v1 in a private browser window. A short JSON answer means we can reach it; a login prompt, a browser check or a "no route" error means we cannot.

Check your spam folder first. If it is not there, make sure the address you signed up with can receive mail from outside your own domain: forwarding-only addresses and freshly registered domains often bounce our message. Sign in to the portal and request a new confirmation email from there. If it still does not arrive, email us from that address and we will look.

Email us before you move, with the old and the new domain. Your account is tied to the store address: our notice that an order is paid goes to the domain we have on file, so until it is updated that notice cannot reach the new site and orders would sit unpaid in WooCommerce even though the money arrived in your wallet. We update the address, you keep the same key, settings and payout wallet, and nothing changes on your side.

Every legal vertical is. CBD, vape, peptides, supplements, adult, forex, gambling, kratom, smoke shops, coaching, prop trading. Because settlement is on-chain, the banking restrictions that get these businesses declined do not apply.

No. There is no underwriting on the merchant, so a prior termination, a MATCH listing or a frozen account elsewhere does not affect whether you can accept payments here.

Yes, and plenty of merchants do exactly that as a backup rail so a freeze somewhere else does not stop them taking orders.

Email us from the address on the account and we deactivate it. Nothing is held on our side, so there is nothing to return: payments already settled stay in your wallet, and open payment links simply stop working.