Checkout expiry
Every checkout has an expiry time. After it passes, the customer can no longer pay and you need to create a new charge.
How the expiry is chosen
Section titled “How the expiry is chosen”NogorPay uses the first of these that is set:
expiry_minutesin the create charge request, from1to1440(24 hours). Values outside that range are ignored.- Your account setting under Dashboard → Integrations → Checkout expiry.
- The platform default of 60 minutes.
The response tells you exactly when the checkout closes, in expires_at, along with server_time and expires_in_seconds.
Choosing a value
Section titled “Choosing a value”| Use case | Suggested expiry_minutes |
|---|---|
| Online store checkout | 15–30 |
| Top-ups and deposits | 10–15 |
| Invoices sent by SMS or email | 720–1440 |
Showing a countdown
Section titled “Showing a countdown”Customer device clocks are often wrong. Base a countdown on expires_in_seconds from the response, not on expires_at compared to the device time:
const deadline = Date.now() + charge.expires_in_seconds * 1000;Detecting expiry
Section titled “Detecting expiry”NogorPay doesn’t send a webhook when a checkout expires, and Verify a charge can still show pending after expires_at. Treat any charge that is pending after expires_at as expired.
