Paytm Gateway

Changelog

1. Version 1.0.17 29 Oct 2026

   - The pending-payment check does nothing at all while a database transaction is open, so closing a failed payment and giving back what it held always happens in its own run.
   - When the database can't say whether a transaction is open, the pending-payment check now notes it in the error log before waiting for its next run.

2. Version 1.0.16 28 Oct 2026

   - On MySQL 8 pending payments are asked about again (the open-transaction check stopped every ask there).

3. Version 1.0.15 27 Oct 2026

   - Reads its keys whether they are stored as typed or sealed by the store, so a later update can keep gateway keys sealed in the database. A sealed key that can no longer be opened counts as not set, and the gateway refuses the payment instead of sending it.
   - A buyer who paid with Paytm and closed the page before returning to the store is now credited: the store asks Paytm about the order before giving up on it.
   - A sealed key that cannot be opened is never sent to the payment provider, even when the store's key-sealing support is missing: the gateway refuses the payment as if the key were not set.

4. Version 1.0.14 23 Oct 2026

   - A Paytm payment Paytm still reports as pending (a UPI or bank payment in progress) now shows the buyer 'Confirming your payment' instead of 'Payment failed', and the request waits for Paytm to be asked before it expires, so a payment Paytm confirms later is credited instead of arriving after the request closed.
   - A Paytm payment still in progress when the buyer comes back is asked about again about 2, 10 and 30 minutes later, then hourly: once Paytm confirms it, the purchase is credited within minutes instead of days, and once Paytm says it failed, the request closes and gives back its held stock and coupon.
   - A Paytm payment confirmed after the buyer switched the request to another payment method is still credited, as Paytm; if the request was already paid another way, it is kept under Payment requests for you to refund instead of being missed.
   - Paytm is no longer asked again and again about a payment it has already answered for: a payment for the wrong amount (kept for review) and a failed one the request can't close on yet are left to the regular expiry check.
   - A Paytm payment that failed while wallet coins were still taken for its request is now closed, and its held stock and coupon given back, as soon as the coins are back, instead of days later.
   - The Paytm pending-payments task log now counts only payments credited to their order as settled; a late, second or held payment kept for you to review is counted separately.
   - A Paytm payment that failed while wallet coins were still taken is closed, once the coins are back, only if the request still waits on that same Paytm payment; one sent to Paytm again or paid another way meanwhile is left as it is.
   - A Paytm payment held for review or for the expiry sweep now remembers which Paytm payment it was about, so a request sent to Paytm again afterwards is never closed because the earlier payment failed.

5. Version 1.0.13 23 Oct 2026

   - A payment settled by Paytm is recorded as paid through Paytm, even if the buyer switched the request to another gateway in a second tab first.

6. Version 1.0.12 23 Oct 2026

   - If you pay with Paytm while the add-on for that purchase is switched off, you now see 'Confirming your payment' instead of 'Payment failed / Try again', so you aren't asked to pay twice.
   - A Paytm payment for an order that was already paid, had closed, or whose add-on is switched off is now kept for you to review or refund instead of being lost or shown as a normal success.
   - A Paytm payment that arrives after its payment request expired, or that pays a request already paid, is now kept under Payment requests for you to refund or fulfil instead of being lost, and a buyer reloading the return page sees their order rather than 'payment failed'.
   - A Paytm payment the buyer completes after you switch Paytm off at checkout is still settled (Paytm sends no other word of it) instead of going to 'payment failed' and being lost.
   - A Paytm return is refused with 'payment failed', recorded nowhere and logged when the Paytm merchant ID or key is not set, or when Paytm's status answer is for another order.

7. Version 1.0.11 19 Oct 2026

   - Check with gateway also reports the id this gateway's return settles the payment under (kernel 1.1.518 settle_reference), read from the provider's own answer, so a request the check settled is not later listed as paid twice when the return reports the same payment.

8. Version 1.0.10 18 Oct 2026

   - When two payments race for one request, the request now records the one that won, and the other is kept for a refund instead of being lost. Needs kernel 1.1.497; on an older kernel it settles as before.
   - A Paytm return for a request already paid by another payment no longer rewrites that request's payment id.