Pay with Vault
Your customers save a card once and pay you in seconds – verified by a text message, settled to you like any card sale.
What is Pay with Vault?

Pay with Vault is a network wallet for the whole Merchant360 ecosystem. A customer saves their card once – at your business or any other business that runs on Merchant360 – and from then on they can pay any Merchant360 invoice, payment link, or checkout with a couple of taps instead of typing card details.
For you, a Vault payment is an ordinary card sale in every way that matters: it runs on your own merchant account, at your own rates, settles into your own deposits, and shows up in Transactions like any other charge. There is nothing to enable and nothing to configure – the Pay with Vault option appears on your pay pages automatically.
The payoff is fewer abandoned payments. Typing a 16-digit card number on a phone is where payments die; a returning Vault customer skips it entirely.

How your customer saves a card
When a customer pays you by card – on an invoice, a payment link, your hosted checkout, or your WooCommerce store – the card form shows an unchecked box: “Save my card with Vault to check out faster everywhere.”
If they check it, their card is saved the moment the payment goes through, tied to the mobile number (and email) on the payment. Every Vault wallet is anchored to a mobile number – if the payment doesn't carry one, the save box simply asks the customer for their cell. That's the whole enrollment – no code to type, no account to create, nothing added to your checkout flow.
Saving is always the customer's choice. The box is never pre-checked, and an unchecked box changes nothing about the payment.

Verification codes arrive only by text – never by email. Filling in the customer's mobile number when you create them means one less thing to type at checkout.
How they pay next time
The code step is the security: nobody can pay with a saved card by just knowing an email address or phone number – they have to be holding the phone. Codes are never sent by email, so access to an inbox alone can't unlock a wallet. The first payment at each new business always requires a fresh code.
- 1On any Merchant360 pay page, the customer taps the Pay with Vault bar at the top.
- 2They enter the email or mobile number their card is saved under – either one works.
- 3A one-time code arrives by text to the mobile number on the wallet. They enter it.
- 4Their saved cards appear as brand and last four. They pick one, tap Pay, and the payment completes.

What you see and what you get
A Vault payment lands in your account exactly like a keyed card sale: same processing rates, same deposit schedule, same receipt to the customer, and the same refund and void controls in Transactions. The transaction detail shows the card brand and last four, just like any sale.
If you run dual pricing, Vault charges the card price – the same price a typed card pays – and the invoice balance reduces by the base amount, identically to your card form.
Chargeback posture is unchanged: it's a card-network transaction on your account, with the added evidence that the payer proved possession of their phone before the charge.
Security and privacy, built in
Card numbers are never stored on Merchant360.
Every use is verified with a one-time code texted to the customer's mobile number before any saved card can be used – codes are never emailed.
Privacy is two-way: you never see where else a customer's wallet has been used, and other businesses never see their payments to you. Customers manage everything themselves at merchant360.net/account – every saved card, every business where the wallet has been used, one-tap card removal, and the option to close the wallet entirely.
When Vault doesn't appear
A few situations keep the Vault option off a pay page, by design: businesses with a card surcharge program (a surcharge is priced from the exact card entered, so those checkouts keep the card form), open-amount payment links where the payer picks the amount, payments covered by a gift card, and test-mode sessions.
None of these affect the rest of your checkout – the card form works exactly as before.
Hosted checkout guide