Vezmo App

Payments

Payment Methods

You control which payment methods your customers can use at checkout — across every surface: the embeddable checkout, payment links, invoices and product pages. Turn Bank transfer (ACH) and wallets (Apple Pay / Google Pay) on or off for your account, from the dashboard or over the API.

Cards are always on — they are the baseline payment method for every account and can't be turned off.

1. The methods

MethodKeyNotes
CardscardVisa, Mastercard, Amex and more. Always on.
Bank transfer (ACH)achUS bank debits. Available only when your account is verified for bank payments and the checkout currency is USD.
Apple PayapplePayOne-tap wallet. Appears automatically for eligible customers on supported Apple devices when enabled.
Google PaygooglePayOne-tap wallet. Appears automatically for eligible customers on supported Google / Android devices when enabled.

Wallets ride on the card rail — they only appear when cards are available and the customer's device/browser supports them. Disabling a wallet hides its express-checkout button; it never affects ordinary card entry.

2. How a method's visibility is decided

A method is shown to your customer only when all three are true:

shown(method) = eligible        // your account can use it (capability + currency)
            AND enabled-by-you  // you turned it on (cards are always on)
            AND not-blocked     // Vezmo hasn't disabled it for your account

New accounts start with every eligible method on. If a method shows Not available yet in your settings, your account isn't verified for it yet — finish verification to unlock it. If Vezmo has blocked a method for risk reasons it appears as Managed by Vezmo and can't be enabled until that's lifted.

3. Control it from the dashboard

Go to VezmoPay → Settings → Payment Methods and toggle each method. Changes apply immediately to every checkout.

4. Control it from the API

Two endpoints, authenticated with a Bearer access token from POST /merchant/api-auth/login. They require the account.read / account.update permissions on your API key (enable these under VezmoPay → Developers).

Get your active methods

Request
GET /v1/merchant/account/payment-methods
Authorization: Bearer <access_token>

Response:

200 OK
{
  "success": true,
  "message": "Payment methods retrieved",
  "data": {
    "methods": {
      "card":      { "enabled": true,  "eligible": true, "blockedByAdmin": false, "toggleable": false },
      "ach":       { "enabled": true,  "eligible": true, "blockedByAdmin": false, "toggleable": true },
      "applePay":  { "enabled": true,  "eligible": true, "blockedByAdmin": false, "toggleable": true },
      "googlePay": { "enabled": false, "eligible": true, "blockedByAdmin": false, "toggleable": true }
    },
    "card": true, "ach": true, "applePay": true, "googlePay": false
  }
}
  • enabled — shown at checkout right now.
  • eligible — your account is allowed to use it (capability active).
  • blockedByAdmin — Vezmo has disabled it for your account.
  • toggleable — you may change it (eligible, not a card, not blocked).

Enable or disable methods

Send any of ach, applePay, googlePay as booleans. Card is always on and is ignored if sent. The response echoes the resulting state.

Request
PUT /v1/merchant/account/payment-methods
Authorization: Bearer <access_token>
Content-Type: application/json

{ "ach": true, "googlePay": false }
StatusMeaning
200Updated — body echoes the new state.
422You tried to enable a method your account isn't eligible for yet (finish verification first).
403The key lacks account.update, or the method is blocked by Vezmo for your account.

5. What the checkout returns

Every checkout/session response includes an enabledMethods object so your own UI can mirror what's offered:

"enabledMethods": { "card": true, "ach": true, "applePay": true, "googlePay": false }

You don't need to act on it — Vezmo renders the correct methods for you — but it's there if you build a custom summary.

6. Good to know

  • ACH is USD-only. Even when enabled, the bank option only shows on USD checkouts.
  • Disabling is instant and everywhere. Turning a method off hides it on the embed, payment links, invoices and product pages at once, and the payment intent won't accept it either.
  • Authentication is unaffected. Method controls only change which options appear — they never bypass 3D Secure / SCA where it's required.