recommendedGateway.session. This is the object you read to send your customer to the gateway’s checkout page.
Reading the session
For redirect-based gateways (Paystack, Flutterwave, Monnify, Korapay), thesession object shares these common fields:
gateway: the gateway that produced the sessionreference: the gateway’s transaction referenceredirectUrl: the checkout URL to send the customer toraw: the raw response data from the underlying gateway
- Send the customer to
recommendedGateway.session.redirectUrlto complete checkout. This works for Paystack, Flutterwave, Monnify, and Korapay. - Store
paymentId. You will need it to check status or verify the payment through Archefusion’s APIs.
Gateway session examples
Thesession object varies by gateway. Expand each gateway below to see the shape of its session object. The raw field is trimmed here for brevity.
Paystack
Paystack
redirectUrl to complete checkout.Flutterwave
Flutterwave
redirectUrl to complete checkout.Monnify
Monnify
redirectUrl to complete checkout.Monnify’s checkout URL contains pipe (
|) characters. Browsers accept these directly, so you can use redirectUrl as-is. If your HTTP stack requires strictly valid URLs, encode the pipes as %7C.Korapay
Korapay
redirectUrl to complete checkout.Interswitch WebPAY
Interswitch WebPAY
redirectUrl is a POST form action. Submit the fields in formFields to redirectUrl as a POST request using method, rather than sending the customer there with a plain GET redirect.
