This automation function for payments will help you reduce the manual work needed to generate and load tokens. If you have an API connected to this process, our automation may not work for you.
To find out more about Token generation and loading, read this articles: Purchases - Token Settings
In order for this automation to work, there must be enough balance for the specific currency in your account. Should there be insufficient, you can convert balances from other currencies in your account. We will be covering this step in this article.
Token Generation
To set up token generation automation:
1. Click Settings, then Automation and finally Payments
If manual token generation has been disabled, you will not be able to manually generate any tokens from your account.
Token Load Schedule
To set up token loading automation, configure it here:
If you choose to configure token load schedule, loading will happen according to the due date of the token and the amount will be according to the rates of the booking. If the booking has 2 rates with different due dates, there will be 2 load schedule.
For tokens who fail to generate, they will be left in drafts. We would suggest to check those tokens and enable manual token generations as mentioned in the previous section.
Conversion
In order for tokens to be automatically generated, there must be available balance in your account for the token to be loaded. You can activate this automation to complement the previous two automations as well. This automation will convert other available currencies (secondary balance) for the amount that is needed to generate the token.
For example:
If the token amount is 100 USD and you have only 90 USD available in the USD balance. This automation will convert another available currency to USD, enough for the shortfall of 10 USD.
You can configure this automation to exclude balances of your choice OR only convert from the list of balances of your choice to convert from.
Tokens loaded by this automation will be labelled as Automation in source.
This automation will convert as many balances as it takes to to load the token fully. Once the token has been loaded fully, the token will be generated.
In the event that the system is unable to obtain enough currencies to fully load the token and this process fails, the token will be saved as Draft which you may choose to revisit at a later date and manually complete this process.
Now, let us explain some of the scenarios that may happen along with the course of your operations.
-
Change in token amount
- This could happen due to refunds in the bookings being activated.
- In this case, the system will check for the rates that has not passed due date and unload the amount accordingly by adjusting the load schedule amount. The process will follow exactly the same as the above process.
-
Booking has been cancelled
- If there is no load schedule
- If the rate has passed due date, the system will not be able to unload the amount. There will be an error in the token, listed under Event
- If the rate has not passed due date and there is sufficient balance in the token to make adjustments, the system will do so.
- If the rate has not passed due date and there is insufficient balance in the token to make adjustments, the system will create a dispute for this token.
- If there is a load schedule
- If the rate has passed due date, the system will not be able to unload the amount. There will be an error in the token, listed under Event and any upcoming load schedule will be deleted.
- If the rate has not passed due date, the system will simply delete any upcoming load schedule.
- If there is no load schedule