The following is a table of guidelines for payment nominal limitations:
|Bank Name||Minimum Payment Amount (IDR)||Maximum Payment Amount (IDR)|
|BNI, BNI Syariah, BRI, BSS, and Mandiri||1||50,000,000,000|
Please be informed that there are maximum limitations for payments via ATM, M-Banking, and Internet Banking where each bank has different policies. Some banks limit it to IDR 25,000,000.
For a Virtual Account with a close-amount, the Virtual Account will only receive payments according to the expected amount. However, in practice, there is still a possibility that your customer can pay the Virtual Account with a nominal other than the expected nominal. The following is a table of guidelines for payments on a Virtual Account with a close-amount. Please note that this is only applied to the aggregator model only.
|Bank Name||From the Same Bank||From Interbank|
|BCA, BNI, BRI, Mandiri, and Permata||The expected amount will be displayed||The expected amount is not displayed, customers can enter a different amount than the set amount|
|BNI Syariah and BSS||The expected amount is not displayed, customers can enter a different amount than the set amount||The expected amount is not displayed, customers can enter a different amount than the set amount|
Transactions on a Virtual Account can be made at any time while the Virtual Account is inactive status. However, if your customer pays using a different bank (i.e. interbank transfer), the sending bank may wait to continue the transaction until the next business hour.
As long as the sending bank of your customer is able to transact and send money to the receiving bank, Xendit will receive a notification (callback) from the receiving bank and process the transaction on our system.
The settlement time for Virtual Account transactions will depend on the commercial model you choose. The following is an explanation of the cooperation model and its relation to settlement time:
|Commercial Model||Settlement Time|
Note: For BCA aggregators, the transaction will be settled in D + 2 working days after the transaction date. Please see Virtual Account Page for full details about our commercial model.
Below is the definition for the possible status for Virtual Account payment in the dashboard.
|Detected||Payment callback has been received by Xendit but the money is not settled yet and unavailable for the customer to withdraw|
|Completed||Payment callback has been received by Xendit and the money has been settled and available for the customer to withdraw|
Several banks have implemented a prefix before the Virtual Account name that will show up when end-user try to pay the VA. Please note that this is only applied to the aggregator model only. The following is a table of prefixes for each bank:
|BCA and BSS||No Prefix|
|BRI||BRIVA + <your_va_name>|
|BNI||XDT + <your_va_name>|
|Mandiri and Permata||Xendit + <your_va_name>|
Bank has a limit for the length of the name which results in the Virtual Account name being truncated if the name exceeds the maximum character when your customer makes a payment. The following is a table of guidelines for character lengths in Virtual Account names:
|Bank Name||Minimum Digit (Character)||Maksimum Digit (Character)|
|BCA (Aggregator Model)||3||50|
|BCA (Switcher Model)||3||30|
|BNI, BNI Syariah, BSS||1||100|
|BRI, Mandiri, Permata||1||20|
The expiration date is the date that a Virtual Account becomes inactive and cannot receive any more payments. Payments made after the Virtual Account has expired will be automatically rejected. Please be informed that Fixed Virtual Account will have 31 years as default expiration time, but you can set it when creating a Virtual Account via API (Please visit virtual account API reference). The default expiration time for Virtual Accounts on xenInvoice is 24 hours.
We currently do not provide a feature that can delete or cancel a Virtual Account. If you need to stop using a certain Virtual Account, we recommend that you update the expiration time to a past time so that the Virtual Account will expire and become inactive.