Create Deposit Request
Recording a request to deposit into a specific bank account: enter the IBAN, and if the inquiry service is enabled, the account holder's name and bank fill in automatically — so you're sure the money is going to the right account.
Step by Step
- Choose the customer making the request.
- Enter the requested currency and amount.
- Enter the IBAN — the holder's name and bank come in automatically (or type them manually).
- Save; carry out the payments later from the deposit request page (all at once or in stages).
Fields
| Field | Description |
|---|---|
| Requesting account | The customer the deposit is being made for. |
| Requested currency and amount | The requested amount. |
| IBAN | Starts with IR followed by 24 digits (26 characters in total). |
| Account holder name / bank name | The destination details; if the IBAN inquiry service is enabled and has credit, these fill in automatically once you enter the IBAN — otherwise, enter them manually. |
| Description | Description of the request. |
Notes
- The automatic IBAN inquiry is a paid service; whether it's enabled and has credit depends on your app's plan/balance.
Automatic IBAN Inquiry
Next to the IBAN field is an "Automatic inquiry" checkbox, on by default for rial forms: the moment you leave the field, the holder's name and bank fill in automatically. If the inquiry doesn't return anything, or you've turned the checkbox off, fill in those two fields yourself.
After the assignment is recorded, a green "Send account number" button appears on the request form, sending the account number and description to the paying party's WhatsApp group.
Two options at the bottom of the form
- WhatsApp notice to the requester: after saving, a message saying "your bank account has entered the payment process" (with IBAN, holder, bank and amount) is sent to the requester's WhatsApp. The text is editable in WhatsApp message templates, and your choice is remembered for next time.
- Request is active (on by default): if you turn it off, the request is only recorded so it isn't forgotten, but it stays out of all processing and allocation lists (dashboard, open items, readiness allocation, statement chip) until you press "Activate" on its page. If the WhatsApp notice was ticked too, the message is sent upon activation.
If another request with the same IBAN was registered in the last 24 hours, an "are you sure?" warning with the previous doc code appears both under the IBAN field and after saving — it is only a warning and never blocks saving; it catches two colleagues accidentally registering the same request twice.
The IBAN field now validates itself: a malformed sheba/IBAN gets an immediate red message and no inquiry is spent; for foreign IBANs, or when the inquiry is off or fails, the bank name is derived from the number itself for a dozen-plus countries (Iran, Türkiye, UAE, Iraq, …) and fills the bank field. Input that is not IBAN-like at all (e.g. a card number) gets no warning.