Curlec FPX Messaging Flow

Created by Shiva S, Modified on Tue, 2 Apr, 2024 at 2:59 PM by Varshini Ravichandran


  1. Via Curlec services, a customer submits a form (API request) to PayNet for creating a mandate/Instant Pay.

  2. PayNet redirects the browser to the customer's online banking portal.

  3. If the customer logs in and completes the transaction, they will be redirected to the merchant URL with a success message.

  4. If the customer chooses to abort the transaction, they will be redirected to the merchant URL with a message that indicates incomplete transaction.

  5. However, in the case where an unexpected error occurs, often due to internet connectivity interruptions, the customer is unsure whether the transaction has gone through. 

  6. The customer might try to perform the transaction againDue to a time lag of sending the AC message from the banking portal/PayNet to us (approx. 2 minutes), the transaction status might not be updated immediately, allowing a duplicated transaction.

  7. Hence, when the customer retries, we will prevent a duplicated transaction by first sending an AE message to check the actual transaction status before proceeding.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article