Payments On the roadmap
Stripe
Stripe is on the roadmap. What exists today is the layer beneath it: the place a second payment provider will fit without the settle path being rewritten.
What is already in place
The payment layer holds a protocol each provider fills in, a separate account resolver per provider, and a callback address carrying the organisation, the account and a secret. The Online betalingen card on an invoice and the hourly reconcile are provider-neutral too. A second provider fills in three behaviours: whether the body of a callback may be believed, whether it is signed, and whether the create call may be replayed.
- The settle path stays invoicing's: a confirmed payment is one ordinary payment line
- The module that collects the money and the module that knows the invoice never read each other's tables
- With one implementation the layer is still a hypothesis, not a proven second path
What you cannot do today
There is no Stripe screen, no key field and no callback address. If you want to collect online today, Mollie is the only connection that exists, and it settles in euros. For an agency invoicing clients outside the eurozone right now, this card changes nothing in practice yet.
What it deliberately does not do
- Nothing is connectable: there is no screen and no place to enter a Stripe key.
- Mollie is the only payment provider schakl. speaks today.
- There is no date on it. The layer beneath exists, the implementation does not.
Where to find it Nowhere yet: there is no Stripe screen and no field for a key.
