Choose how to take payments
Compare hosted checkout, embedded checkout, card fields, payment links, invoices, mobile apps and the WooCommerce plugin by the front-end work they need, what your customer sees, the payment methods they offer and how you learn the result.
Overview
Every way to take a payment with Vezmo ends in the same place: a payment in VezmoPay › Transactions, the same webhook events and the same Payments API. They differ in how much you build and where your customer pays.
Card details never reach your servers in any of them: Vezmo's checkout or its secure fields collect them.
Compare the options
| Option | Front-end work | What your customer sees | How you learn the result |
|---|---|---|---|
| Hosted checkout | None. Your server creates a session and sends the customer to its url. | A checkout page hosted by Vezmo, with your business name. | payment.success webhook; the customer comes back to your successUrl with paymentId and status. |
| Embedded checkout | A script tag, a container and your own Pay button. Your site must be in Trusted origins. | Vezmo's payment form inside your own page, in a frame. | Browser events (success, pending, error) for your page; the webhook for your server. |
| Card fields | Most: you build the checkout page and mount Vezmo's secure payment field in it, styled to match. Your site must be in Trusted origins. | Your own checkout page, with Vezmo's payment field. | The result of confirm() for your page; the webhook for your server. |
| Payment links | None. Make a link in the dashboard or with POST /merchant/paylinks. | A Vezmo checkout page for one amount, opened from a link you send. | payment.success; the link shows Paid. |
| Invoices | None. Send one from the dashboard or with POST /merchant/invoice. | An emailed invoice with a page to pay it. | invoice.paid and payment.success. |
| Mobile apps | Checkout for apps: open the hosted checkout in the phone's secure browser sheet, no SDK. | The hosted checkout. | The webhook; your app's return link carries status, and paymentId unless the payment failed. |
| WooCommerce | None. Install the plugin and select Connect with VezmoPay. | Vezmo's payment form on your store's checkout, in a frame, or a Vezmo checkout page. | The plugin updates each order from the webhook. |
Payment methods
- Hosted checkout, embedded checkout and mobile apps offer cards, Apple Pay and Google Pay, and every other method you have turned on that fits the payment: US bank payments, pay-later methods and the customer's own currency where available.
- Card fields offer cards, Apple Pay and Google Pay, US bank payments and most of the other methods. A few are on the hosted and embedded checkout only; the Elements reference lists them.
- Payment links and invoices offer the same payment methods as hosted checkout.
Which methods you offer is set per business. See Payment methods in the API reference.
Which one to pick
- You have a website and want the least work: hosted checkout. One API call and a redirect.
- You want your customer to stay on your page: embedded checkout. Add your site to Trusted origins first.
- You want full control of the page's layout: card fields.
- You don't have a website, or you bill clients by email: payment links and invoices, from the dashboard. No code.
- You sell in an app: checkout for apps.
- You run a WooCommerce store: the plugin. Connect with VezmoPay generates a key for you, which turns off your current key of that mode (see API keys).
The parts they share
- One session API. Hosted checkout, embedded checkout, card fields and mobile apps all start with the same server
call,
POST /merchant/secure-payments. Moving between them changes a few fields of that call, not your server's design. - Webhooks. Ship orders on the
payment.successevent, never on a browser event or a redirect alone. See Webhooks. - Test mode. Every option works with a test key and test cards. See Test mode for developers.
Related
Facts checked against the product on 9 Nov 2026.
Was this page helpful?
Test mode for developers
How a test key runs your integration in the sandbox on the same base URL, how test and live data stay apart, the livemode flag, emails in test mode, what isn't simulated, and test values for cards, 3D Secure, declines, disputes and bank payments.
Hosted checkout
Take a payment on a checkout page Vezmo hosts for you, with one server call and a redirect, covering the session fields, the customer details, expiry, theme, success and cancel redirects, app return links, your order number and Idempotency-Key, fulfilling from the webhook and the session limit.