1. Introduction

VanturaPay is a secure payment aggregation platform that enables merchants to accept digital business payments seamlessly through a single endpoint integration.

What this manual covers:
  • End-to-end customer interface payment flows
  • Merchant operational cycles & validation rules
  • Comprehensive REST API development structures
  • Asynchronous callbacks and system-to-server webhooks
  • Automated standard settlements & mass payouts

2. System Overview

The platform coordinates communication securely across four standard actors:

1. Customer (End User)

Initiates point-of-sale checkout operations inside the registered business application environment.

2. Merchant Account

The corporate entity leveraging VanturaPay systems to receive incoming client clearings securely.

3. VanturaPay (Aggregator / PayFac)

Orchestrates payment initialization engines, verification layers, ledger settlements, and financial routing.

4. Payment Gateway (Flutterwave)

Executes structural underlying operations spanning Cards, Bank Transfers, USSD strings, and digital mobile Wallets.

3. Payment Flow (High-Level)

1

Checkout Selection

The customer confirms billing requirements inside the partner interface.
2

Payload Generation

The merchant system pushes programmatic payload criteria out to the VanturaPay core endpoint.
3

Provider Initialization

VanturaPay requests routing infrastructure context from upstream partners (Flutterwave).
4

User Processing

The client executes authentication routines safely against chosen settlement channels.
5

Provider Webhook Hooking

Upstream switches dispatch validation pings directly back to the VanturaPay backend.
6

Ledger Audit Checks

VanturaPay isolates transaction instances and confirms funds balance capture rules state.
7

Merchant Redirection Event

VanturaPay notifies the target application callback hooks asynchronously with fresh data objects.
8

Settlement Execution

Cleared capital batches transition structurally straight into the merchant ledger pools.

4. User (Customer) Experience

Payment Steps
1. Click Pay
2. Secure Checkout
3. Pay Mode
4. Success
5. Auto Redirect
Customer Redirection Parameter Structure

Upon transaction resolution, users route straight back to the merchant site using clean URI query parameters:

https://merchant-site.com/payment-status?status=success&reference=TXN12345

5. Payment Links

VanturaPay Payment Links allow merchants to accept payments without deep functional application layout integration. A secure hosted payment page is generated on demand and shared directly via WhatsApp, SMS, Email, or social networks.

Primary Use Cases
  • Merchants executing operations without websites
  • Instant standalone billing and one-time custom invoices
  • Social messaging checkout interactions
  • Distributed remote or field sales processing
Operational Path
  1. Generate a link via the Administration UI or programmatic APIs.
  2. VanturaPay stands up a unique public hosted resource URL token.
  3. The end client interacts with the endpoint directly from any device browser.
  4. The transaction processes safely within the payment engine.
  5. Automated real-time notifications fire down configured merchant system logs.
Live URL Resource Archetype
https://merchant.vanturapay.com/MP-LINK-8F3K92

6. Merchant Onboarding Guide

6.1 Data Registration Demands
  • Corporate Entity Name & Base Address Required
  • Verified Support Email & Phone lines Required
  • Valid Local Bank Clearing Allocation Target Required
  • Target User Return Routing Callback URL Optional
  • Asynchronous Server Webhook Delivery Hook Optional
6.2 Account Status Lifecycles
  • Pending Identity verification / Document audit queue.
  • Approved Fully operational. Processing active.
  • Suspended Temporary administrative operational holds.

7. Merchant Dashboard Features

The web administration application gives operational teams administrative insights over system parameters:

Real-time Monitoring
Settlement Records
Live Ledger Balances
Bank Targets Matrix
Hook Request Logs
CSV / PDF Exports

8. Developer Integration Guide

8.1 Authentication Criteria

All payload transaction initialization parameters must include the following distinct headers:

X-API-Key: Private alphanumeric signature hash.
X-Contract-ID: Structural identification identifier.
8.2 Payment Initialization API
POST /api/v1/payment/pay.php
Field Param Data Type Required Functional Scope Description
merchant_idstringYesUnique application profile target identifier.
amountnumberYesTotal order clear processing value inside currency unit (NGN).
customer_namestringYesFirst and last identification details of target client.
customer_emailstringYesTarget destination customer standard communication inbox address.
referencestringYesStrictly unique application transaction sequence reference index hash.
redirect_urlstringYesDestination site route target for browser execution redirection.
Initialization Integration Example (HTML / Standard Forms)
<form action="https://vanturapay.com/api/v1/payment/pay.php" method="POST">
    <input type="hidden" name="merchant_id" value="MERCHANT123">
    <input type="hidden" name="fw_subaccount_id" value="A47VD&dbNC290C">
    <input type="hidden" name="amount" value="5000">
    <input type="hidden" name="customer_name" value="John Doe">
    <input type="hidden" name="customer_email" value="john@example.com">
    <input type="hidden" name="redirect_url" value="https://merchant.com/return">
    <button type="submit" class="btn btn-success">Pay Now</button>
</form>

9. Callback (Redirect) Handling

Scope Purpose: Safely return the web client interaction interface context over to the merchant software viewport cleanly following asynchronous execution.

Sample Form Callback String Properties
status=success
reference=MP-20260108-12345
amount=27580.00
Critical Merchant System Implementation Actions:
  • Isolate the query reference attribute securely.
  • Validate current tracking parameters against VanturaPay status endpoint arrays.
  • Modify downstream target business order fulfillment tables explicitly.

10. Webhook Integration (Server-to-Server)

System Purpose: Asynchronous immutable event verification streaming. Ensures application logic updates trigger even if user viewport windows disconnect.

Endpoint Setup Rule: Configured natively within the core administration portal options dashboard.
Expected Webhook Event JSON Data Payload
{
    "event": "payment.success",
    "reference": "MP-20260108-12345",
    "amount": 27580.00,
    "status": "PAID",
    "merchant_id": 2
}
Structural Payload Verification Process
  • Inspect validation signature metrics or secure authorization token lines inside payload objects.
  • Query structural references against double-allocation parameters to eliminate double processing risks.
  • Commit order logging status properties securely straight to local storage engines.

11. Reports & Exports

Programmatic data pipelines accept query parameter structures to allow seamless parsing of accounting information:

My Transactions Log Matrix (Standard Comma-Separated Values) .csv supported

12. Security & Compliance

HTTPS TLS_1.3
Key Auth Tokens
Hook Verification

13. Error Handling

The system drops explicit exception flags alongside industry-standard JSON format declarations when validations fail:

Invalid Authorization API Key
Malformed Callback Serialization
Duplicate Reference String Exceptions
Insufficient Active Ledger Clearances

Note: Exceptional application flags stream cleanly into your system management logs for runtime debugging.

14. Support & Contact

Need engineering assistance with your integration? Reach out across our developer channels:

Email Helpdesk
Dashboard Tickets
Online Documentation

15. Versioning

Document Release version: 1.0
System Track Revision Date: 1st January, 2026

VanturaPay – Simplifying Payments, Powering Growth