Nudge Changes
POLi™ Nudge
The POLi™ nudge ensures that the merchant receives a real-time notification that a transaction has reached a terminal state.
Refer to The POLi Nudge for more information.
POLi™ will nudge the Merchant in two separate occasions for some PayID transactions if the Customer’s financial institution is holding the funds for 24 hours or more for security reasons. One nudge for PaymentPending and the second nudge to notify (Failed, ReceiptUnverified, TimedOut or Completed).
Successful Scenario
Error Scenario
Key Notes and Delayed Payments Config!
Notes from POLi™ Developers:
When a merchant receives a status as “PaymentPending”, the Customer needs to be notified that requested merchant service will be issued upon settlement confirmation (for example, issuing of flight tickets, topping up a digital wallet, remittance).
{warning} Important
Transactions with a Warning The merchant should not consider “PaymentPending” status as transaction is completed. Because payments are delayed or held up, there is no guarantee that payments will be processed and settled quickly before 24 hours, it is up to the merchant to consider whether it wishes to take the risk of rendering the service or deliver the goods in such case.
If the second status is not completed (timeout, Failed, ReceiptUnverified) merchant should let the customer know that the funds have not settled and the transaction has failed. POLi™ will not generally send any immediate notifications to the customer post the outcome of the payment, however POLi™ will show the appropriate message at the end of the transaction if the payments are held up or delayed. The merchants can make the changes accordingly and notify the customer separately to match with their internal process.!
Once a merchant has upgraded the integration to handle the new terminal status “PaymentPending” and to handle dual nudges for same transaction. POLi™ will enable delayed payments to the specific merchants.
Delayed Payment Configurations:
Once the POLi™ transaction reaches a terminal state, POLi™ initiates a transaction request and provides provision to merchants to configure the below redirect URLs.
Refer to Initiate Transaction API for more information.
| Result | Description |
|---|---|
| SuccessURL | The complete URL to redirect the customer to if the transaction is successful. |
| FailureURL | The complete URL to redirect the customer to if the transaction is not successful. |
| CancellationURL | The complete URL used to redirect the customer to if they cancel the transaction. |
| NotificationURL | The complete URL where POLi™ will deliver the Nudge POST. |
However, for “PaymentPending” status the Redirection URL should be configured in POLi™ Console. The Redirection URL for Payment Pending will have the POLi™ transaction token as Query string parameter.
| Result | Description |
|---|---|
| Delayed Payment URL | The complete URL to redirect the customer to if the transaction is in Payment Pending State. |
Transaction Status
POLi™ transaction status records the progress of a transaction throughout the payment process. Each status represents a critical point in the transaction and each has to be reached before the customer can progress to the next and ultimately complete the transaction. There are two categories of transaction statuses:
| Category | Description |
|---|---|
| Active | Attained during the course of a transaction before reaching a terminal status. A transaction with an active state is not considered finished |
| Terminal | Attained when the transaction has reached a conclusion either successfully or unsuccessfully |
| Status | Category | Description |
|---|---|---|
| Initiated | Active | When a transaction is started, it is immediately assigned the status Initiated |
| FinancialInstitution Selected | Active | A transaction moves into the FinancialInstitutionSelected status when the user has selected the Financial Institution that they wish to use |
| EulaAccepted | Active | When the user accepts the POLi End User License Agreement, the transaction moves into EulaAccepted |
| InProcess | Active | This status is reached when the customer hits the login page of the bank they have selected |
| Unknown | Active | The transaction goes into Unknown status when the user clicks on the Confirm button to make their payment. The result of the payment is pending |
| Completed | Terminal | A successful transaction where the internet banking receipt has been issued by the bank. The POLi system has recognised this and notifies the merchant via the GETTransaction API. Funds are expected to settle for this status |
| Cancelled | Terminal | When the user cancels the transaction it will move into Cancelled status |
| Failed | Terminal | The Failed status occurs when a transaction experiences a non recoverable problem, such as; a bank specific problem, a bank connection dropout or a communication error. There could have also been a problem with the POLi system at the time |
| ReceiptUnverified | Terminal | A rare state attained when the POLi system could not confirm whether the user’s payment was successful. In this case, the funds may have been transferred but the user will not be displayed a receipt from POLi or the merchant. This status can arise due to a bank issue or a local issue to the user |
| TimedOut | Terminal | Automatically attained when the customer has not completed the transaction before the POLi timeout and the transaction is not currently in Unknown |
{warning} Important
Transactions with a Completed status typically result in a credit to the merchant’s bank account.
Transactions in Failed, Cancelled and TimedOut statuses typically will not result in a bank account credit.
The status ReceiptUnverified indicates that there is uncertainty whether the purchasing customer’s bank has processed the payment instruction, e.g. because communications were lost at a critical time.
All other statuses indicate that the transaction is still ongoing.