Vorgio as a payment provider
Vorgio is an invoicing tool. The payment-provider integration turns Vorgio into a checkout option for your customers: when one of your shoppers selects "pay by invoice" at checkout, your shop calls Vorgio, Vorgio creates the customer record + a numbered invoice, and emails the invoice to the customer. Your shop is notified via webhooks when the invoice is sent and (later) when it is marked paid.
This is how "Kauf auf Rechnung" / "open invoice" works in DACH, packaged for any shop platform.
#Who owns what
| Concern | Owner |
|---|---|
| The customer's contact data, the invoice itself, the legal retention | Vorgio (the merchant's Vorgio team) |
| The order, the product catalogue, fulfilment | Your shop |
| Bank-side payment (the customer transferring money) | The customer's bank → the merchant's bank |
| Reconciliation ("this invoice has been paid") | The merchant, by marking the invoice paid in Vorgio (manually or via your shop's plugin once its own processor confirms) |
Vorgio is not a payment processor. No card data, no PSD2, no SCA. Money moves out-of-band by SEPA transfer (the invoice carries an EPC QR code with the merchant's IBAN).
#Two integration paths
#Server-to-server (recommended)
Your shop's server calls Vorgio. The Vorgio API token never leaves your server.
1Customer → Your shop checkout → Your shop server → Vorgio API → invoice email to customer
2 ↓
3 webhook back to your shop
This is the path the PHP SDK and the WooCommerce plugin use. It's the simplest, most secure, and fastest to integrate. Pick it unless you have a strong reason not to.
#Browser-side via the JS widget
If you don't have a server-side checkout flow (e.g. a static-site shop using only client-side JavaScript), use the JS widget. The widget never holds your API token — instead, your thin server (or a small serverless function) creates a one-shot checkout intent and hands the browser a client_secret that's tied to that single intent. The browser then asks Vorgio to confirm the intent, and Vorgio creates + sends the invoice.
You still need some server-side capability for this — even if it's a single Cloudflare Worker or Vercel function — because creating the intent requires the secret API token.
#What you need to start
- A Vorgio account and at least one team. (Sign up at the main Vorgio site if you haven't.)
- An API token issued from your team's settings page with the "Payment-provider integration" preset. See Getting started.
- A webhook endpoint on your server that can receive
invoice.sentandinvoice.paidevents. See Webhooks.
#What this guide covers
- Getting started — issue a token, make your first call
- The /v1/checkouts endpoint — the one call that does everything
- Webhooks — receive delivery/payment events with verified signatures
- Clients & external_id — find-or-create semantics
- Metadata — round-trip your shop's order ID
- Rate limits — defaults, the floor, and how to handle 429s
- Error reference — RFC 7807 problem types
- PHP SDK —
vorgio/vorgio-php(preview) - WooCommerce plugin — drop-in for WP shops (preview)
- JS widget — browser-side checkout via
@vorgio-app/vorgio-js - Going live — production checklist
- Test mode — exercise the full API against production Vorgio without real side-effects
For raw endpoint shapes (request/response/headers) see the auto-generated /api-reference.