Customers pay by card on a checkout page, and your system marks the booking confirmed or the invoice paid within moments. Deposits, instalments, subscriptions and refunds, without anyone matching payouts by hand.
Stripe is a card payments platform with a public API. It offers hosted or embedded checkout pages, shareable payment links, subscriptions and invoices, and it is available to businesses in Malta. You can use all of it from its dashboard, and for a handful of sales a month that is often enough.
Connecting it to your own system means your system, not a dashboard, knows who paid what and for which job. The important part is the return trip: Stripe tells your system by a signed message (a webhook) when a payment succeeds, fails or is refunded, and the system updates the booking, the invoice and the customer’s record without a person in the middle.
The order or booking is created in your system first, then the customer is sent to a Stripe checkout page for that exact amount. If they abandon it, you can see an unpaid booking and follow up, instead of finding nothing.
Take a deposit when a slot is booked and request the balance later, with both payments recorded against the same job. It suits a booking system where no-shows cost real money.
Every invoice carries a pay-now link, and the link goes by email or WhatsApp. When it is paid, the invoice closes itself. See quoting and invoicing for the wider picture.
Recurring plans with trials, upgrades and failed-payment retries, with the member’s access switching on and off from the payment status.
Payment plans for larger amounts and discount codes the team can create without a developer. Both are decisions about rules in your own system, with Stripe doing the card part.
Staff refund a payment from the customer record, the amount is checked, Stripe is told, and the books show a credit note. No second login, no retyping a payment reference.
What is sold, when a deposit is due, how VAT is shown, what happens on a refund. These rules live in your system, and getting them written down is the longest conversation.
The server decides the amount and creates the checkout or payment link, so a customer can’t change a price in their browser. Requests that might be retried carry an idempotency key, which stops a network hiccup creating two charges.
Stripe’s webhooks are verified against their signature, answered quickly and processed from a queue. Stripe retries failed deliveries for days in live mode, can send the same event twice and doesn’t guarantee order, so every handler is built to be repeated safely.
Everything is run end to end in Stripe’s test mode before real money moves. After launch, a scheduled check compares Stripe’s records with your system and alerts when they disagree.
I haven’t published a deposits or subscriptions build for a named client yet. Checkout, instalments and coupons at MCMA are the closest, and they are running live.
Stripe checkout, instalment plans, coupons and automatic payment reminders for a music academy, with live checkout tested end to end at launch.
Read the case study Second-hand retail · Built & deliveredSecondhand MaltaA storefront with cart, Stripe checkout, delivery zones and order emails, built and delivered for Secondhand Malta.
Read the case study Local services marketplace · Live · web & iOSQabbadStripe is among the integrations of this marketplace. Payment between customer and provider stays between them, so I don’t offer it as a marketplace-payments example.
Read the case studyYes. Stripe lists Malta among the countries where businesses can sign up. You need a Maltese business (or sole trader) with the usual identity and bank details for payouts.
Yes, and the rules live in your system: how much, when, and what happens if the balance isn’t paid. The quote builder prices deposits at about 4 to 8 extra hours on top of the 17 to 30 for a payments module.
That is why the webhook is the source of truth, not the customer’s browser. Stripe retries for days, and a scheduled check compares Stripe with your records, so a missed message turns up as an alert instead of an unexplained gap.
Yes. Each invoice gets its own payment link, the webhook confirms the payment, and the system marks the invoice paid. Part payments are recorded against the same invoice.
Either works with a custom system. I compare them on the Viva Wallet page, and sometimes the answer is to support both.
Quotes from your rate card, invoices with VAT, deposits and automatic chasing.
ServiceBooking systemsOnline booking with your rules: deposits, reminders, waitlists and calendar sync.
ServiceClient portalsA secure login for clients: invoices, documents, bookings, payments and messages.
ServiceWebsites for systemsFast, search-ready sites with forms, calculators and bookings wired into your system.
GuideMalta VAT invoicesThe details a Malta tax invoice must carry, and what that means for invoicing software.
IntegrationViva WalletViva Wallet checkout and payment confirmation tied to your tickets, bookings and invoices.
IntegrationXeroInvoices, payments and contacts synced between your system and Xero, with no retyping.
Case studyMCMAA music academy run end to end from one platform: applications, scheduling, payments, portals and programmes.
Case studySecondhand MaltaPhotograph an item, get a listing: an AI scanner that writes the copy and researches the price.
PagePricingHow a custom system is priced: what moves the number and typical build times.
PageIntegrationsWhatsApp, Stripe, Xero, Google Workspace, Microsoft 365, Shopify, Wix and more.
The quote builder opens with Stripe already selected. Add the rest of your system and I reply with a fixed quote.