When you send an invoice, 3650HQ generates a dedicated virtual bank account for that specific order. The customer transfers into it like any normal bank transfer, and the invoice is automatically marked paid once the payment is verified. No screenshots, no manual receipt checking.
Each virtual account is generated per invoice and is a real bank transfer destination, verified server-to-server before an invoice is marked paid, so a fake payment screenshot can't fool the system. Payments are processed via Monnify's Direct-to-Account infrastructure.
In most of West Africa, the default way to pay a small business is a bank transfer. Not a card, not a checkout page, not a wallet. The customer opens their banking app, types in an account number, and sends the money. That behaviour is not going to change because a piece of software would prefer it did.
What that leaves the seller with is a verification problem. The customer sends a screenshot of a successful transfer. The seller has to decide whether to believe it. The honest ones wait, refresh their banking app, squint at a list of credits that all look alike, and try to work out which one corresponds to which order. The less patient ones ship on the strength of the screenshot, which is exactly the gap that doctored screenshots exist to exploit.
Neither version scales. Checking transfers by hand is a job that grows linearly with orders, and it is the job that gets dropped first on a busy day, which is how orders end up shipped unpaid and paid orders end up unshipped.
When you send an invoice, 3650HQ generates a virtual bank account for that one invoice. It is a real transfer destination, generated through Monnify's Direct-to-Account infrastructure, and the customer pays into it exactly as they would pay any other business.
The difference is that the account number itself identifies the order. There is no matching step, because there is nothing to match.
Because the destination is unique to the order, a credit arriving on it can only mean one thing. Reconciliation stops being a task somebody performs and becomes a property of how the payment was collected.
3650HQ does not read screenshots and does not take the customer's word for it. The invoice is marked paid only after the payment is confirmed server-to-server. A doctored screenshot has nothing to fool, because no part of the system is looking at one.
No checkout page, no card details, no account to create, no app to install. They copy an account number and send a transfer, which is the thing they already know how to do. Payment friction is where DM sales die, and the lowest-friction payment method is the one the customer already uses.
The virtual account is a collection destination tied to a specific invoice, not a replacement for your bank account. Funds settle to your own account.
Payment links are the usual answer to getting paid in a chat, and they solve a different problem. A link takes the customer out of the conversation and onto a checkout page, where they are asked for card details or to authorise a transfer through an interface they have not seen before. Every one of those steps is somewhere the sale can stop.
A transfer to an account number does not move the customer anywhere. They stay in WhatsApp, switch to their banking app for fifteen seconds the way they would to pay a friend, and come back. The seller is not asking them to learn anything or trust a new page, which matters when the business they are buying from is someone they found through Instagram.
There are two separate flows in 3650HQ and it is worth being clear about which is which. Money from your customers arrives through the virtual accounts described above and settles to your bank account. That is your revenue and 3650HQ does not sit on it.
Separately, 3650HQ itself runs on prepaid credits that you top up in your own currency, which is what pays for messages sent, audio transcribed and AI used. Those are different systems handling different money, and a quiet week on the credit side costs you nothing while your customer payments carry on regardless.
Yes. Send an invoice and 3650HQ generates a dedicated virtual bank account for it. The customer transfers in and the invoice is marked paid automatically once verified.
Yes. 3650HQ generates a dynamic virtual bank account per invoice through Monnify's Direct-to-Account infrastructure.
3650HQ never trusts a screenshot. Every payment is verified server-to-server with Monnify before an invoice is marked paid.
No. The virtual account is a collection destination tied to a specific invoice; funds settle to your own account.
No. A new one is generated per invoice. That is the whole point: because the destination is unique to the order, a payment arriving on it identifies itself, and there is no reconciliation step to get wrong.
No. The customer pays into the invoice's virtual account, not your own account number, and the funds settle to you afterwards.
A payment link moves the customer onto a checkout page and asks them for card details or a new authorisation flow. A virtual account asks them to do the thing they already do every day: send a bank transfer. Fewer steps, and none of them unfamiliar.
No. Virtual accounts are collection destinations for specific invoices and funds settle to your own bank account. The prepaid credits that run 3650HQ itself are a separate system entirely.