Payments
AgnusPAY
Payments, payout schedules and fees. What your customer sets up, and the one thing your site reads.
AgnusPAY is the payments layer under every order. Your customer onboards once, picks the methods they want and gets paid on a schedule. Almost none of that is your problem: from a storefront, AgnusPAY is one public endpoint that says what can be paid with today.
This page exists because the answers to "why is the checkout button hidden" and "when does the money arrive" both live here.
What a storefront reads
/api/public/{organizationId}/payment-methodsPublicThe methods available right now, online and in person.
Two more keyless endpoints read what is on this page without being about payments: the fee list, and the quote on Online Ordering, which prices a basket using these fees, the delivery zone and the tax configuration in one answer. Everything else here happens in the dashboard, behind a signed-in session, and cannot be reached with an API key.
Onboarding
AgnusPAY runs on Stripe. Your customer accepts the agreement, then completes Stripe's onboarding: business details, an identity check and a bank account. Cnter tracks how far along they are and reflects it back in the dashboard.
| State | Means |
|---|---|
pending | Onboarding started, verification not finished. No payments yet. |
active | Verified and able to charge. Payment methods appear. |
paused | Temporarily switched off by your customer. Methods come back empty. |
inactive | Deactivated. Same effect, deliberately harder to undo. |
Verification is not instant and can ask for more documents after it looked finished. A site built during onboarding will see empty payment methods and should handle that as a normal state rather than a bug.
Payment methods
Online methods are enabled per organization and depend on what the account is approved for: iDEAL, Mastercard and Visa, Apple Pay, Google Pay, Bancontact, Klarna, Link and Revolut Pay. The buyer sees them on the Stripe payment page, in their own language.
Custom methods are the pay-in-person ones your customer writes themselves: "cash at the counter", "card on delivery", "invoice". Each has a title and a description, and each has an id you pass as custom_payment_method_id at checkout. That path creates the order immediately as unpaid, and staff marks it paid when the money arrives.
Fees
Order fees are amounts added on top of the items: packaging, a service charge, a tip. Your customer defines them and your storefront reads them from the public fees endpoint. A restaurant’s delivery fee is not one of these — it belongs to the delivery zone the address falls in, so it is not in that list and cannot be. It is not invisible, though: quote the basket and it arrives as a line in fees[] like any other, already counted in the total. A cart that never quotes is a cart where the buyer first meets the delivery fee on the payment page.
| Property | Effect |
|---|---|
type | fixed for an amount, percentage for a share of the subtotal. |
is_required | Always applied. Display it, do not offer to remove it. |
is_variable | The buyer picks the amount, passed in fee_overrides. |
sort_order | The order your customer arranged. Render in it. |
Fees are taxed at their own rate rather than the order's average, which is why the tax breakdown is something the server hands you rather than something you assemble. The quote returns it while the customer is still shopping and the checkout returns it again at the end. See Tax.
Payouts
Money is collected per transaction and paid out on a weekly schedule. Each payout groups the week it covers and separates the parts, so a bank line can be reconciled without guesswork.
| Figure | Meaning |
|---|---|
| Gross volume | What buyers paid in that week. |
| Stripe fees | The processing cost. |
| Agnus fee | The 0.8% platform fee and the transaction fees, VAT included. |
| Net volume | What is left after both. |
| Payout amount | What actually lands in the bank account. |
Every payout carries PDFs: the transactions it covers, the fees taken, and a total. Your customer downloads them for their bookkeeping, or exports a period as a file. Upcoming payouts are shown before they settle, so the next transfer is not a surprise.
A payout is pending until the bank confirms it and paid afterwards. Bank timing is bank timing, so a Friday payout is not a Friday arrival.
Agnus Cloud transaction fees
The transaction fees belong to AgnusPAY, the payment product of Agnus Cloud. Every organization pays the same tariff and there is nothing to configure. This part is for the organization itself, not for a storefront: a site does not have to do anything for it.
- Per online payment
- 0.8% + €0.50 excl. VAT
- Per third-party order
- €0.50 excl. VAT
- Manual payments
- Free
- Minimum per month
- None
With 21% VAT, €0.50 is exactly €0.61. The tariff applies to every organization since 1 November 2026. Nothing is charged retroactively: only orders from that moment count.
Which orders cost €0.50
| Order | Costs €0.50 |
|---|---|
| Paid online through AgnusPAY | Yes, next to the 0.8% of that payment |
| Received through a delivery platform such as Thuisbezorgd or Uber Eats, once that integration exists | Yes |
| Paid manually: cash, card on delivery or bank transfer | No, free |
| Entered in the dashboard, or pushed through the API with its own payment | No, free |
| Partly refunded | Yes, the order went ahead |
| Disputed by the buyer, also when the dispute is lost | Yes, the order went ahead |
| Cancelled or fully refunded, at any moment | No |
| An online checkout the buyer did not finish | No, it never becomes an order |
When an order is cancelled after its fee was already withheld or invoiced, you get the amount back as credit. The credit is deducted from the next withholding and shown on the next monthly invoice.
How it is withheld
- For an online payment, the €0.50 and the 0.8%, both with VAT, are part of the fee on that payment itself. They come off the payout, so there is nothing to transfer.
- Third-party orders are settled with your next payout: we withhold their fees together with your next online payments. At most half of a single payment goes to settling.
- Stripe, the invoice and the reports show the same amount: 0.8% plus 21% VAT for an organization in the Netherlands, and €0.61 per transaction.
- Under Settings → Organization → Payments every payout shows what Agnus Cloud withheld from it, and a block shows the current month: orders, amount, withheld, and what is still to settle or held as credit.
- Without AgnusPAY nothing can be withheld. The fees for third-party orders are then on the monthly invoice, which you pay by bank transfer.
Monthly invoice
Every month you receive an invoice from Agnus Cloud for that month: the number of orders, the amount excluding and including VAT, what has already been withheld, and what is still to settle or held as credit. Owners and admins download every invoice under Settings → Organization → Reports & invoices.
VAT
| Organization | VAT on the transaction fees |
|---|---|
| In the Netherlands | 21% |
| In another EU country, with a VAT number from that country | 0%, VAT reverse-charged |
| In another EU country, without a VAT number | 21% |
| Outside the EU | 0%, not taxed in the Netherlands |
VAT is rounded per order: 21% of €0.50 is €0.105, which becomes €0.11. The country and VAT number come from your organization profile, so keep them up to date.
Transactions and balance
Every charge appears as a transaction with its buyer, amount, method and status, and the running balance shows what is collected but not yet paid out. Both are dashboard screens for your customer, not endpoints for your site.
If a site needs order-level financial data, read it from the orders API with read_orders, which is scoped and auditable. There is no key-authenticated path to the payments ledger, on purpose.
Pausing, deactivating, handing over
- Pausing stops new payments while leaving history and payouts intact. Meant for a closed season or a dispute.
- Deactivating is the deliberate end of it. Both make the public payment methods endpoint return empty.
- Ownership can be transferred to another member, which is what happens when a business changes hands. The payment account moves with the organization, not with the person.