Integrations

Connect QR2Stripe to the system you already run.

Booking system, e-shop, ERP, CRM, accounting or a spreadsheet. QR2Stripe is built on a small, open protocol, so every payment taken on your phone can start in your system and end up back in it, without anyone copying a number.

Why connect it at all

Every place where a person copies data between two systems is a place where mistakes happen and time disappears. When QR2Stripe is connected, the amount comes from your order, the payment carries your reference, and your system learns about the payment by itself. No retyping at the counter, no list of orders to tick off, no unmatched payments at the end of the month.

Three ways to connect, from no code to made to measure

No code: the app webhook

After every payment the app sends the details to an address you choose: your server, n8n, Make, Zapier or anything that accepts a web request. Set up in the app in minutes.

More about the app webhook

Your developers: the open protocol

Your system shows the payment QR and receives Stripe’s signed confirmation. The protocol is documented, small and the same one the WordPress plugin uses.

More about the protocol

Done for you: custom integration

We build the connection for your system and your way of taking payments, test it and hand it over. AI-assisted development keeps it fast and affordable.

More about custom integration

The app webhook: every payment, straight into your tools

Switch it on in the app under Merchant settings → Webhook after payment and enter an address. From then on, every successful payment is sent there with its reference, amount, currency, time and Stripe payment ID. It works with every way of connecting, including a simple website with the embed script that has no server of its own.

Fits any receiver

JSON, form or plain text; GET, POST or PUT; your own headers and body template with variables such as {reference} and {amount_decimal}.

Does not lose payments

No signal? The app retries and keeps undelivered calls in a queue on the phone. A unique key on every call lets your receiver ignore a repeat.

Signed and tested

An optional signing secret proves the call came from your phone. Send test call checks the whole chain before your first real payment.

Ideas to start with: add every payment as a row in a spreadsheet, mark the booking paid in your reservation system, post a message to your team chat, or create a payment entry in your invoicing software.

The open protocol: built for developers

Any system that can do two things can take payments with QR2Stripe: show a payment QR code, and receive Stripe’s signed webhook. Everything else is standard Stripe.

  • API mode. The QR carries only a one-time token. The app asks your server for the payment details, so the amount always comes from you and cannot be tampered with. Three small endpoints, documented request by request.
  • Inline mode. The QR carries the amount and the reference itself, and your system needs no endpoint at all. Ideal when the system cannot expose an API; the operator confirms the amount on the phone.
  • Your Stripe account, your rules. Payments are created in your own Stripe account with your reference attached, and your system marks them paid only after Stripe’s signed confirmation matches the order.
  • A working reference. The WordPress plugin implements the whole protocol, so your developers have running code to compare with, not just a specification.

The protocol description is available to every developer. Ask us for it at [email protected], or see the documentation.

Done for you: we build the integration

Prefer not to touch code? We adapt the terminal and the integration to your system and to the way you take payments: your references, your statuses, your notifications. Thanks to AI-assisted development this is faster and cheaper than classic custom development, because the protocol is documented and much of the code can be generated, then reviewed and tested by a person.

  • Booking and reservation systems: collect the balance on arrival and mark the booking paid.
  • E-shops and order systems: payment on pickup or delivery, with the order updated instantly.
  • In-house applications: an employee creates the payment, the customer pays on the spot.
  • Accounting and invoicing: every Stripe payment recorded against the right invoice automatically. See our custom integration service, which runs on your own server.

How we work together

1. You describe it

Which system you use, what you charge for and how the payment should be recorded. A short message is enough.

2. We agree the scope

You learn what the integration involves and how many hours it will take before any work starts. Custom development is EUR 30 per hour, with no VAT added.

3. We build and test

Everything is tested with Stripe test payments, never with live money.

4. You go live

We switch to live mode together with you and hand over the code and the documentation.

Questions

What is the difference between the app webhook and Stripe’s webhook?

Stripe’s webhook comes from Stripe, is signed by Stripe and needs a public endpoint on your server; it is the strongest proof of payment. The app webhook comes from your phone right after Stripe confirmed the payment to it, so it also works for websites without a server. For high-value orders, check the payment in Stripe before you hand over the goods; we can build that check for you.

My system is not WordPress and has no API. Can it still work?

Often yes. If your system can show the amount and the order number on a web page, the embed script can create the QR, and the app webhook can report the payment back. Tell us what you use and we will find the simplest way.

Do you see our payment data?

No. Payments go to your own Stripe account and the integration runs in your system or on your server. Card data is handled by Stripe and never reaches the app, your system or us.

Is there an iPhone version?

The app is available for Android today and an Apple version is in preparation. The protocol and the integrations do not depend on the phone, so what you build now will work with both.

Let us look at your system

Write a few lines about the system you use and how you want to take payments. We will reply with the simplest way to connect it and what it would involve. Write to [email protected].