Platform Comparisons
Fake Bank Alerts: Verify the Payment Before Dispatch

To reduce fake bank alert fraud in Nigeria, release goods only after confirming payment through your bank or an authenticated payment-provider record. Dynamic virtual accounts can connect transfers to specific orders, but account generation alone proves nothing. Baci documents configurable payment gateways; this exact automated workflow still needs merchant-level verification.
Decision summary
A screenshot, forwarded receipt or customer’s debit notification should never be the authority for marking an order paid. Your release decision needs evidence from the receiving side, matched to the right order and amount. This applies whether you sell through WhatsApp, a storefront or a physical counter.
Automated checkout verification changes who supplies that evidence. Instead of asking dispatch staff to judge a customer’s image, a properly implemented checkout obtains transaction information from the payment provider. Staff then need a clear rule for which verified orders qualify for release.
This guide uses official Baci, Paystack and Kora documentation reviewed on 21 November 2026. It explains documented mechanisms and recommended operating controls; it does not report a completed Baci checkout test, measured fraud reduction or guaranteed protection against every payment risk.
Feature comparison: manual transfers and verified checkout
| Decision point | Transfer to a personal or business account | Provider checkout with a dynamic account | Baci evidence and limits |
|---|---|---|---|
| Payment evidence | Staff must independently check the receiving bank’s record. | The integration can obtain a provider transaction result. | Payment options are configurable; the exact deployed verification flow requires confirmation. |
| Order matching | Staff reconcile the credit against the order. | A temporary account can be tied to a transaction reference. | Do not assume every configured gateway exposes this channel. |
| Amount checks | Staff compare the received amount with the amount due. | The integration must compare the provider result with the expected payment. | Demonstrate handling of mismatches before relying on automatic confirmation. |
| Setup burden | Requires receiving-account access and a reliable checking procedure. | Requires provider approval, configuration and working event handling. | Country, currency, eligibility and provider setup apply. |
| Dispatch control | A designated person authorizes release after checking funds. | Release should depend on an authenticated, matched payment result. | Staff access exists; exact permissions and entitlements need checking. |
| Costs | Check your bank’s applicable terms. | Check provider collection fees and who bears them. | Subscription pricing is separate from provider charges. |
The practical distinction is reconciliation. A business bank account can support a sound manual process, while a poorly configured automated process can still make mistakes. Choose the workflow your team can verify and enforce, including when a customer is waiting at the counter.

A customer’s receipt and receiving-side payment confirmation serve different purposes.
Checkout and payments: what dynamic accounts actually verify
The account number identifies the payment destination
Paystack’s Payment Channels documentation describes Pay with Transfer as a temporary bank account tied to the customer’s transaction, available to eligible businesses in Nigeria and Ghana. Kora’s Bank Transfers guide describes temporary, single-use dynamic accounts for NGN payments. Kora requires an activated account and separate activation of its Bank Transfer API feature.
Generating that account is a request for payment. It is not confirmation that money arrived. The customer still has to complete the transfer, and the provider must report the outcome. Avoid copying a previous customer’s temporary account into a new WhatsApp conversation: use the details generated for the current payment attempt.
The provider result supplies the payment evidence
A webhook is a notification sent from the provider’s server to the merchant’s system. Paystack’s Webhooks documentation requires verification of the event’s origin. Kora likewise warns against acting on counterfeit notifications. An integration must authenticate these messages before using them to update payment records.
Paystack’s Verify Payments documentation also distinguishes a successful API request from a successful transaction. Receiving a valid response does not itself mean the customer paid: the integration must inspect the transaction status. Kora’s Bank Transfers guide recommends querying the transaction before giving value to the customer.
For a merchant, the useful question is concrete: “Show me which provider transaction makes this order paid.” A reassuring animation, customer redirect or generated receipt is insufficient unless it follows the verified payment result.
Successful payment still needs an amount match
Paystack’s Accept Payments guide instructs integrations to check the amount before delivering value. Kora’s amount-handling documentation distinguishes the requested amount, expected amount and actual amount paid. Expected payment can include fees when the customer bears them.
Consider an illustrative order costing ₦28,000 including delivery. A confirmed payment of ₦25,000 should trigger review rather than full dispatch. Likewise, a second notification for the same payment should not produce a second parcel. These are separate controls: payment success, sufficient payment and one-time fulfillment.
Build the expected total from the agreed order, delivery charge and applicable checkout charges. Staff should not improvise the amount during handover. If the customer changes the basket or delivery method, reconcile the payment against the revised order before authorizing release.
What Baci supports, and what remains unverified
The current Baci features page documents configurable Paystack, Korapay, Credit Direct and pay-on-delivery options, with country, currency, eligibility and provider limitations. It also describes staff-entered orders, payment records, order documents and team permissions.
The reviewed implementation register supports these capabilities at code level. It does not establish that dynamic-account generation, authenticated confirmation and dispatch blocking work together in production for your merchant account. Provider documentation explains provider mechanisms; it does not prove Baci has enabled every mechanism.
Baci’s mission is to make practical commerce infrastructure more accessible to African merchants, starting with Nigeria. Bringing payment configuration and order work into a commerce platform addresses a concrete operational need: giving staff a consistent place to manage a sale. That ambition remains distinct from verified deployment and measured impact.
Before adopting this particular workflow, request a demonstration using your intended gateway, currency and staff roles. Ask which payment channel customers actually see, which result changes the order status, and whether manually recorded payments are distinguishable from provider-confirmed ones. Do not infer those answers from a gateway logo.
A release procedure for store owners and dispatch staff
The following is an editorial operating recommendation. It describes the controls to establish, rather than claiming every step is an available Baci automation.
- Create one identifiable order. Record the products, delivery charge, customer contact and total before requesting payment. Give staff an order identifier they can use throughout the handover.
- Send the current payment instructions. Where an eligible checkout provides temporary account details, direct the customer to that payment attempt. Explain any displayed expiry and expected amount.
- Wait for receiving-side confirmation. A screenshot may help investigate a problem, but it should not authorize release. Check the authenticated provider result or the receiving bank’s transaction record.
- Match the payment. Confirm the order reference, amount and currency. Investigate mismatches instead of assuming a similarly sized credit belongs to the waiting customer.
- Authorize dispatch once. Record who approved release and whether the order has already been handed over. Keep payment confirmation separate from packing and delivery progress.
- Reconcile unresolved cases. Assign pending payments, duplicate payments and refunds to a named person. Keep the transaction reference with the case so the next shift can continue it.
For WhatsApp sales, a useful customer message is: “We’ll confirm your order after checking the payment against its reference.” This sets the expectation before the rider arrives. Give dispatch staff a consistent escalation route so urgency does not become an informal exception to the rule.

Payment verification and dispatch approval need a consistent handover procedure.
Handle delays and exceptions without guessing
The customer was debited, but the order is pending
A pending result is unresolved. Paystack documents pending and ongoing transaction states separately from success. Ask the responsible staff member to investigate the existing reference before requesting another payment. A second transfer can create a separate reconciliation problem.
Do not automatically accuse the customer of fraud. Preserve the order, explain what is awaiting confirmation and provide a clear next update. A genuine transfer problem and a fabricated receipt require different responses, even though neither justifies releasing an unverified prepaid order.
The payment arrived late or for the wrong amount
Paystack’s Pay with Transfer support guidance warns that late transfers and incorrect amounts can cause failure. Expiry behavior is channel-specific: follow the current checkout instructions rather than teaching staff one universal account lifetime.
Kora’s Developer FAQ explains that virtual-account success notifications can carry the actual amount paid even when it differs from the expected amount. A success label therefore cannot replace reconciliation. Check the rules of the precise payment product your merchant uses.
A notification repeats or someone records payment manually
Both providers document webhook retries. Kora recommends tracking processed notifications to avoid duplicate delivery of value. Merchants should ask how their integration prevents repeated updates from causing repeated fulfillment.
Manual payment recording needs its own approval rule. If a staff member can mark an order paid after seeing an image, that action can bypass the intended control. Confirm permissions and review procedures during setup; a generated receipt records an action, but does not independently establish receipt of funds.
Pricing and cost model
Baci’s published pricing page, reviewed on 21 November 2026, lists Free at ₦0, Pro at ₦5,000 per month and Premium at ₦15,000 per month. Free lists a ten-product maximum. Premium lists multiple staff accounts. Confirm the subscription and permissions required for your intended workflow before choosing a plan.
Pro displays “No Transaction Fees.” Do not interpret that wording as a promise that payment providers or banks charge nothing. Obtain separate confirmation of Baci charges, gateway collection fees, taxes where applicable, and who bears each charge. No provider fee rate or settlement timetable is quoted here.
Budget for setup work as well as subscriptions: provider onboarding, staff training, exception handling and reconciliation time. The useful cost comparison is between complete operating procedures. This guide has no measured evidence for a particular merchant’s savings, loss reduction or return on investment.
Use the current Baci pricing page to confirm published terms, then request a written explanation of any payment-channel requirements that are not specified there.
Best fit
Verified checkout is a sensible workflow to evaluate when several people handle an order, customers commonly pay remotely, or dispatch staff cannot independently access receiving-account records. Its operational value depends on everyone recognizing the same release authority.
A small owner-operated shop may continue with manual transfers if the owner checks actual credits and reconciles each order consistently. That approach carries more manual work, but it should be assessed on its controls rather than dismissed simply because it lacks automation.
If connectivity or provider service is interrupted, establish a hold-and-review procedure. Do not silently switch prepaid orders to pay on delivery or treat a verbal assurance as confirmation. Any change in payment terms should be deliberate, recorded and understood by the customer and dispatch team.
Verdict
Choose authenticated payment evidence and reliable order matching over screenshot approval. Compared with manual transfers, dynamic-account checkout can connect payment attempts to orders, but it adds provider setup and exception-handling requirements. Baci is worth evaluating for its documented payment and order-management surfaces; confirm the complete merchant workflow before relying on automatic release.
Three controls matter most: confirm the receiving-side result, reconcile the expected amount, and authorize fulfillment only once. Those are practical steps toward reducing fake-alert exposure. No account number, platform subscription or integration label can honestly guarantee the elimination of all fraud.
FAQ
Can dynamic virtual accounts eliminate fake bank alert fraud?
They can reduce reliance on customer-supplied receipts when paired with authenticated provider confirmation, order matching and release controls. Generating an account alone does not confirm payment or eliminate every fraud risk.
Does Baci automatically verify every bank transfer?
Baci documents configurable payment gateways, but the reviewed evidence does not establish automatic verification for every bank transfer or merchant. Confirm the enabled payment channel, provider configuration and deployed order-confirmation workflow for your account.
Should dispatch release goods after seeing a debit alert?
For a prepaid order, wait for receiving-side confirmation matched to the correct order and amount. A customer’s debit alert can support an investigation, but should not authorize dispatch by itself.
Are payment-provider charges included in Baci’s subscription?
Do not assume they are. Baci subscription pricing and provider collection charges are separate questions. Confirm applicable gateway fees, who bears them and the exact subscription entitlement before activation.