Connect each payment with a record staff can check.

Agree the transaction details

Confirm who is selling, what the customer receives, approved currency displays, invoice information, payment terms and refunds. Your finance team and qualified advisers decide tax and any e-invoicing requirements.

Handle more than a successful response

Keep pending, confirmed, failed, repeated, reversed and refunded outcomes clear. A missing browser response should not automatically be treated as a failed payment. Match the order with the provider's record.

Give staff a way to follow up

Make unmatched payments and delayed updates visible. Agree who handles refunds, disputes and settlement checks and which records are needed for accounting.

Test using approved tools

Use an authorised test environment and fictional records. Check repeated clicks, delayed confirmation, interrupted connections and refunds without using real identity or banking credentials.

See the CBN and other official starting points for your responsible team's questions, or discuss the payment flow.