Sync Payment Statuses between Sana and PSP
Sana Commerce Cloud integrates with different payment service providers (PSP) across the world, such as Sana Pay, PayPal, Authorize.Net, Docdata, WorldPay, etc. They allow to accept payments from the webstore customers online. The payment service providers process the credit / debit card payments online.
When a customer places an order and pays for it, the order payment goes through different stages. These stages define the status of each payment transaction.
For more information about payments and payment statuses supported by Sana, see Payment Statuses.
The task Sync payment statuses between Sana and PSP is used to synchronize payment statuses of the sales orders between Sana and the payment service provider.
Set Up the Task Sync Payment Statuses between Sana and PSP
To set up the task Sync payment statuses between Sana and PSP, click Edit.
The table below provides the description of the task settings:
|
Settings |
Description |
|---|---|
|
Run on schedule |
Use this option to enable automatic running of the task according to the configured schedule or disable it to allow only manual start of the task. If you enable Run on schedule, you should enter either the interval in minutes when the task should run automatically or the fixed time. |
|
Run interval (in minutes) |
Enter the time interval in minutes when the task should run automatically. |
|
Run time |
Enter a fixed time when the task should start automatically. Use the time picker to set the desired time. The user’s local time zone is used. |
|
Send e-mail to administrator when task has failed |
Use this option to enable or disable e-mail notifications when a scheduled task fails. If the scheduled task has failed, the webstore administrator receives an e-mail with the name of the task that failed, the name of the webstore, which is useful in case you have several webstores, when the task failed, and the error message. Thanks to this, the webstore administrator can quickly respond to problems with data synchronization. |
|
Maximum items to skip before failure* |
Enter the maximum items to skip before failure. When some payment statuses cannot be synchronized for some reason, this value indicates how many payment statuses can be skipped before the task fails. |
|
The maximum count of days that payment transactions are valid* |
Enter the maximum number of days that payment transactions are valid. If payment status of the transaction remains the same during this period, the task stops checking the status of this payment transaction. |
|
Maximum archived log files |
Enter the maximum number of log files to store. If this number exceeds, the oldest log file will be removed and the new one will be created. |
