IntegrationsPayments
Taking money from your customers. Online payments are not available in the beta yet: issue invoices and record the payments you receive elsewhere.
Online payments are not available in the beta. GENV takes no card details and cannot charge your customers; invoices, payments and credits are recorded and the money moves somewhere else.
Practice payment gateway
practice moduleGENV's own stand-in. It opens a demonstration payment page for one invoice and sends GENV a signed event saying what was chosen there, so the whole invoice-and-pay path can be rehearsed — including a lost or repeated confirmation. No card is read, no money moves, and no invoice is ever marked paid by it.
demo.gateway
Stripe Checkout
in betaBuilt and not yet switched on in the beta: a customer pays an invoice on Stripe's own page, into the business's own Stripe account, and GENV counts the payment only after Stripe's signed notice and GENV's own question to Stripe agree. Not yet certified against Stripe.
stripe.checkout
Razorpay Payment Links
in betaBuilt and not yet switched on in the beta: a customer pays an invoice on Razorpay's own page, into the business's own Razorpay account, and GENV counts the payment only after Razorpay's signed notice and GENV's own question to Razorpay agree. Not yet certified against Razorpay.
razorpay.links
The invoice-and-pay path can be rehearsed end to end on GENV’s own practice gateway, which takes no money and can never mark an invoice paid. How the two collection models differ
Before you connect one
- Issue a credential for GENV alone, with the narrowest privileges that work. Why, and how to rotate it
- Check the connection, which is a read and changes nothing.
- Read what the module says it will send. Each adapter names its own operations rather than claiming a generic capability.
- A saved connection is not a verified one, and GENV says so on the connection itself.