How it works
The full journey of an invoice, from issue to confirmed transfer
No payment gateway, no redirect, no card number. The principle is that of an ordinary bank transfer — virement.tn simply organizes the request, the tracking and the confirmation.
1. The organization issues the invoice
An organization (merchant, school, condominium manager, leasing or insurance company, association…) creates an invoice: amount, debtor identified by their phone number, category, due date. It can do so manually from the app, in bulk by import, or automatically through the API.
An organization must have at least one verified RIB (Tunisian bank account identifier) checked by the virement.tn team before it can issue an invoice — otherwise creation is refused. This guarantees that money can only be directed to a controlled account.
2. The debtor is notified
The customer receives a notification (app, SMS or email depending on their preferences) about a new payment request. They can review the invoice details, the issuer, the amount and the due date before acting.
3. Confirmation — with or without a validation code
For a customer who is already identified (recurring subscriber, insured person, tenant on a leasing contract…), under a ceiling set by the organization, the invoice can be confirmed automatically, with no code. In other cases — typically a one-off purchase from a merchant — the customer provides a validation code: 6 characters, single-use, valid for 24 hours, which they find in their own virement.tn space. This code proves their consent and moves the invoice to “confirmed” without being a payment — the invoice stays “awaiting payment” until the next step.
4. The customer makes the transfer
From their own banking app — not from virement.tn. No banking data goes through the platform: the customer picks their beneficiary (the organization's verified RIB) and confirms the amount already agreed.
5. The bank confirms, the organization is notified
As soon as the debtor's bank confirms execution, virement.tn marks the invoice “paid” and notifies the organization — in the app, by email, or through a signed webhook for a technical integration. It is this confirmation — not the creation of the invoice, nor the validation code — that should trigger delivery of a good or a service.
And for payments in several installments?
The same journey applies to every installment of an installment payment plan, a leasing contract or a recurring payment: each installment is an invoice, paid by a transfer the customer makes themselves.
Why “confirmed” does not mean “paid”: see confirmed vs paid invoice. For open-amount collections, see the group fund and open-amount QR.
Frequently asked questions
Can virement.tn automatically debit my bank account?
No. Every transfer is made voluntarily by the payer, from their own banking app. virement.tn never holds, or asks for, access to payers' bank accounts.
Do I need a bank card to pay an invoice?
No. Payment is made by an ordinary bank transfer from your bank's app — no card number is ever entered on virement.tn.
What happens if the organization's RIB is not verified?
It cannot issue invoices until the virement.tn team has verified at least one of its RIBs — a safeguard against creating invoices that point to an unchecked account.
Are there uses other than standard invoicing?
Yes. Three optional modules work on the same principle of direct bank transfer: the open-amount QR (the payer chooses the amount), the group fund (with a displayed goal) and the dawra (rotating contributions among friends and family).
Ready to try virement.tn?
The Free pack lets you issue up to 10 invoices a month with no commitment, so you can test the whole process from start to finish.
Create a free account