- Your backend creates a checkout session.
- Payfonte returns a checkout URL.
- You redirect the customer to that URL.
- Customer completes payment and Payfonte notifies your system via webhook.
Why Use Standard Checkout?
Fastest Launch
Minimal frontend complexity. Your backend creates a checkout and redirects users.
Hosted Experience
Payfonte handles payment method UI and provider-specific interactions.
Reliable Status Updates
Use webhook events and transaction verification for final payment outcomes.
Integration Steps
1
Collect payment details on your backend
Prepare required fields like
amount, currency, country, and customer information.2
Create checkout session
Send a request to
POST /payments/v1/checkouts with your client-id and client-secret.3
Redirect customer
Redirect users to
data.shortURL (or data.url) from the response.4
Confirm final status
Process webhook notifications and/or verify transaction status before order fulfillment.
Create Checkout Request
Parameter Reference
Amount Rule (Important)
Payfonte does not support decimal API amounts. Send integer minor-unit values only.500.00 NGN->500001250.75 NGN->125075
After Redirect and Payment
Customer redirect result
Customer redirect result
After checkout, customer is redirected to your
redirectURL with transaction context such as status and reference.Webhook notification
Webhook notification
If webhooks are configured, Payfonte sends asynchronous status updates to your webhook endpoint.
Final state verification
Final state verification
For critical flows, verify transaction status from your backend before shipping goods or crediting wallets.
Failed payment handling
Failed payment handling
If payment fails, allow user retry and keep your order state pending until final success is confirmed.
Production Best Practices
Related Docs
Inline Checkout
Embedded checkout alternative for on-page payment.
Webhooks
Set up and validate payment event callbacks.
API Reference
Endpoint and schema details for checkout operations.