Create or simulate a merchant advancement request. To trigger a simulated advancement request, you must include confirm_advancement=false in the query string. If you specify true, the advancement request becomes an actual request, not a simulation.
The endpoint enables a merchant to simulate an advancement scenario in order to validate whether or not there is enough balance in the account, as well as how much tax is anticipated. Since a simulated advancement is not a real advancement, it is not processed.
A merchant advancement is sometimes called a prepayment of receivables. You arrange to have a financial institution make regular deposits into your account equal to what you expect to receive in the future from credit card sales in installments or post-dated
checks and bills. The financial institution deducts its fee before it puts the money in your account. You pay back each deposit when you receive
payment from your customers. This is a way of covering business expenses in the short term. It's a cheaper alternative to a loan.
Note:
- If the merchant is the head merchant (also called a centralizer), the advanced amount is given to the head merchant instead of individual branch merchants, this is designed for better manageability.
- If the commercial establishment is not registered as a headquarter or a branch in the current marketplace, the advancement is for a single commercial establishment.
- The merchant must have sufficient balance in the account for the specified date range of the advancement.
This endpoint generates a Merchant advancement request created event.
When a merchant advancement transaction is created, the endpoint produces Merchant transaction created and
Merchant advancement transaction created events.