Payments

What it does

Cart and checkout across membership fees, tickets and enrollments.
Payments broken into line items, so one checkout can cover several things.
Membership subscriptions with start and expiry dates and grace periods. Renewal is a reminder plus a payment the member makes — nothing is charged automatically and no card is kept on file.
Per-organization gateway configuration and credentials.
Offline payment recording with administrator verification.
Refunds recorded against the original payment.
Scheduled dues reminders.
Branded invoices and receipts as PDFs.

How a payment flows

cart → checkout → gateway → confirmation → payment recorded → subscription or registration updated → receipt available

Gateways also notify the platform directly, so a payment is still recorded when the member closes the tab before returning. That path is slower, which is why a payment can take a few minutes to appear.

Gateways

Paystack and Stripe are supported, configured per organization so each collects into its own account. Card details are entered at the gateway and never reach the platform.

Where it lives

Permissions

Permissions required

payment:list,read,refund
offline_payment:verify
subscription:list,read,create,update
payment_settings:read,update
gateway_credential:create,read,update,delete

Organization owners and staff accounts have these already. If a screen is missing for you, ask an owner to add the codenames above to your role.