FOR TEAMS BUILDING IN NIGERIA

A payment.
A reference.
A clearer record.

Connect an NGN collection to the order, invoice or delivery it belongs to. Evaluate a focused payment flow with VelvPay’s API.

Discuss your payment flow Read the API reference

Access is subject to business onboarding and provider availability.

ONE REFERENCE, END TO ENDIllustrative flow

YOUR BUSINESS REFERENCEorder_2048Retained in your own system

01
COLLECT
Request an NGN payment
Fixed amount · temporary virtual account
02
CHECK
Look up the payment status
Match the result to your reference
03
RECONCILE
Update your payment record
Handle final-state events and exceptions

Your productVelvPay API

Built around a real business flowSoftware platformsCommerce teamsLogistics operations

FROM COLLECTION TO CONTEXT

The transfer is only
part of the story.

Your product needs to know what was paid, which record it belongs to and what still needs attention. Start with one collection workflow your team can evaluate end to end.

01 /

Collect against a purpose

Evaluate fixed-amount, temporary NGN virtual accounts for a specific payment request. Keep your order or invoice reference alongside the payment record.

02 /

Resolve the payment state

Use reference-based status lookup to distinguish pending activity from a confirmed result before changing an order or releasing a service.

03 /

Keep operations in the loop

Plan around merchant-wide final-state webhooks and reconciliation checks. Route unmatched or unresolved activity to a review queue.

Confirm the available account lifecycle, supported states and event contract during technical evaluation. Production use depends on onboarding and the applicable provider setup.

START WITH ONE USE CASE

Where does a payment
meet your product?

Bring the workflow your team wants to improve. Keep the first evaluation small enough to test properly.

Order-to-payment matching

For commerce teams connecting a payment request to an order before fulfilment.

Invoice collection tracking

For software teams mapping a collection status back to a customer invoice.

Delivery payment records

For logistics teams linking a collection reference to a job and its operational record.

A PRACTICAL START FOR DEVELOPERS

Design the record
before the callback.

Use this short checklist to shape your first evaluation. These are integration planning checks, not a substitute for the current API contract.

Open the technical reference

Build a small, testable first flow.

A Node.js starter, integration guide and six offline mock tests. No signup required.

Explore the developer starter

Map your referencesStore your business reference and returned payment identifiers together. Decide how retries and duplicate requests map back to the same business record.Keep pending separate from paidDo not release goods or mark an invoice paid just because a collection request was accepted. Confirm the final payment outcome.Make event processing idempotentConfirm event verification with the team. Handle repeated or out-of-order notifications without applying the same business action twice.Build a reconciliation pathUse status lookup to check unresolved records. Define how your team investigates mismatches, timeouts and missing notifications.Keep credentials on your serverUse the approved credential flow. Never place secrets in browser code, a support email or a public repository.

Planning checklist only. Your selections stay on this page and are not submitted.

BEFORE YOU COMMIT

A technical conversation
with a clear agenda.

Your payment flowWhat a customer pays for, and what your product should do next.
The integration contractReferences, amounts, account expiry, statuses and webhook handling.
Operational readinessOnboarding, provider availability, test access, fees and a suitable rollout plan.

A FEW USEFUL ANSWERS

Before we talk.

Can we start with just one flow?

Yes. The evaluation can focus on one NGN collection use case and its reconciliation path. Bring an example order, invoice or delivery workflow without real customer data.

Is this a permanent account for each customer?

The flow described here uses fixed-amount, temporary virtual accounts. Confirm account expiry and payment rules with VelvPay before designing your integration.

Can we include vendor payouts?

Discuss payouts as a separate requirement. Vendor payouts are asynchronous and depend on provider availability and setup. Do not assume an accepted request means a completed payout.

What do we need before going live?

Complete the applicable business onboarding and confirm provider access, the current technical contract, fees and operational checks. This page is an invitation to evaluate a flow, not a promise of production access or a launch date.

How should we prepare for the conversation?

Describe your product, the payment problem and one proposed flow. Include how you currently reconcile payments. Do not send API keys, customer records, banking credentials or other secrets.

LET’S START WITH YOUR WORKFLOW

What should happen
after your customer pays?

Tell us about your product and the NGN collection flow you want to evaluate.

Discuss your payment flow

Send a technical enquiry through our form.
Or email hello@velvpay.com.

Please don’t include credentials or customer data. See VelvPay’s Privacy Policy.

A payment.A reference.A clearer record.

Request an NGN payment

Look up the payment status

Update your payment record

The transfer is onlypart of the story.