Integration · Viva Wallet

Viva Wallet payments, inside your own system.

Customers pay on Viva’s hosted checkout, and your system confirms the ticket, booking or invoice when the payment lands. Next to Stripe, or instead of it.

Viva Wallet is a European card payments provider, with card terminals and online payments. It has a developer API for creating payment orders, a hosted payment page called Smart Checkout, and webhooks that tell your system what happened.

Connecting it to your own system works in much the same way as other payment providers. Your system creates the order and sends the customer to pay. Viva tells your system the result, and your system confirms the booking or ticket. If you are weighing it against the other option, see the Stripe page; the two can sit side by side.

What you can automate

Viva Wallet, wired into your system.

Checkout for tickets and bookings

The system creates a payment order for the exact amount and sends the customer to Viva’s hosted page. On payment, tickets or confirmations are issued automatically. Nothing depends on the customer’s browser getting back to your site, which matters most when tickets sell out and people pay from a phone on poor signal.

Member pricing and promo codes

Prices, member discounts and codes are calculated on the server, so a customer can’t edit a price on their own screen. The payment order is created for the amount your system has worked out.

Refunds from the admin screen

A refund is issued from the order in your system, the amount is checked and the record is updated. Staff don’t go to a second dashboard and copy a reference across.

Invoices with a pay-now link

An invoice in your system carries a link that opens a payment order for that invoice, and a confirmed payment closes it. See quoting and invoicing.

Organiser payouts and statements

If you take payments on behalf of others, such as event organisers or tutors, your system can total sales per organiser and produce a payout statement. Viva moves the card money; your system keeps the account of who is owed what.

Stripe and Viva side by side

Some businesses offer both, or switch provider without changing the rest of the system, because the payment layer is its own module. It also keeps you from being tied to one provider.

How it’s built

Connected, then watched.

  1. 01
    Choose the flow

    Hosted checkout is the simplest and keeps card details off your site. Other options exist for recurring payments and saved cards, and we pick the least complicated one that does the job.

  2. 02
    Build against the demo environment

    Viva provides a separate demo environment alongside the live one. Credentials, endpoints and webhook settings are separate for each, so the whole flow is run end to end with test payments before live money moves. Refunds and failed payments are tested too, not only the happy path.

  3. 03
    Confirm by webhook, not by redirect

    A customer who closes the tab after paying never reaches your thank-you page. So the system waits for Viva’s payment-created webhook, matches it to the order using its order code and transaction ID, and only then issues the ticket. If your endpoint doesn’t answer successfully, Viva retries.

  4. 04
    Monitor

    Orders still unpaid after a set time are checked against Viva, and an alert goes out for payments that arrived without a matching order. Payments are reconciled against your records on a schedule. Every payment keeps its Viva reference on the order, so a customer who says “I paid” can be answered in a minute, not an afternoon of searching.

Worth knowing
  • Viva’s fees, contract terms and account approval are between you and Viva. They are not part of my build price, and approval can take time, so open the account early.
  • Some hosting setups need a small proxy in the payment path. MusicPlayground’s runs on Cloudflare Workers. I check early how your hosting will talk to Viva, so it doesn’t surprise you late.
  • If you only take payments over the phone or at a terminal, you don’t need an API connection. It earns its place when payments must confirm a booking, ticket or invoice automatically.
FAQ

Questions, answered.

Should I use Viva Wallet or Stripe?

Use the one you already have an account with, or that your accountant and bank prefer. Both work with a custom system, the cost is mostly in the rules around payment, and the payment layer can be swapped later.

Can customers pay in instalments or save a card?

Stripe and Viva each have ways to save a card for later, with different rules and fees. Tell me what you need, and I’ll check what your Viva account allows before I promise it.

What happens if a customer pays and closes the tab?

The webhook still arrives, so the ticket or booking is confirmed anyway. That is the whole reason payments are confirmed by webhook, not by the customer’s return to the site.

How long does it take?

The quote builder puts an online payments module at roughly 17 to 30 build hours, on top of the 30 to 50 hours of shared groundwork. Refunds, promo codes and payout statements add to that.

Can you add Viva Wallet to a site that already takes Stripe?

Yes. The checkout offers both, or the provider can be chosen per product, and the payments are recorded in one place either way.

Start here

Get a fixed quote.

The quote builder opens with Viva Wallet already selected. Add the rest of your system and I reply with a fixed quote.

Logo