Skip to main content
Nuvion accepts payments from your users through the funding sessions API. Your server creates a funding session; depending on the rail, the user completes it via a hosted checkout redirect, a USSD prompt on their phone, or an email from Interac. Nuvion notifies you via webhook once the session settles.
  • Open Banking: the user is redirected to a hosted bank transfer checkout. Supports GBP and EUR.
  • Mobile money (momo): the user completes a USSD prompt on their supplied msisdn.
  • Stablecoin: the user is redirected to a hosted crypto checkout.
  • Interac: the user receives an email from Interac to complete the payment.

Create a funding session

Use POST /funding-sessions, setting funding_type for anything other than Open Banking (which is the default). See Create a funding session for the full request and response field reference.

Transaction limits

Most currency and rail combinations do not enforce fixed transaction limits. The rails listed below do. Minimum and maximum are stated in main currency units for readability only; amount itself is always submitted in the smallest currency unit.

Mobile money channels

For momo, meta.channel must be one of:

Response

For Open Banking and Stablecoin, redirect the user to checkout_url. For mobile money, the user completes a USSD prompt on their phone; no redirect is needed. For Interac, the user completes payment via an email from Interac; there’s no checkout_url to redirect to.

Update a funding session

After the customer completes an Interac transfer, call PATCH /funding-sessions/{id} to validate the transfer and progress the session’s status. This applies only to interac funding sessions and takes no request body. See Update a funding session for the full response field reference.

Check a funding session’s status

Use GET /funding-sessions/{id} to check the latest status while waiting for a webhook. failure is present once status is failed or expired; check failure.code against the funding session failure codes.
See Retrieve a funding session for the full response field reference, or List funding sessions to page through sessions for an account.

Funding session statuses


Webhooks

Listen for funding_sessions.updated to receive real-time status changes. See Event types for the full payload schema, and Webhooks for delivery and retry details.
Verify a funding session’s status with Retrieve a funding session before treating a payment as settled, rather than relying on the webhook payload alone. See Verifying webhook signatures to confirm the event itself is genuine.

What’s next

Funding Session API reference

Full endpoint documentation for creating, updating, and retrieving funding sessions.

Accept a payment

The other ways to accept payments: account details and card payments.

Event types

Full payload schema for funding_sessions.updated and every other webhook event.