What changed, and when.

FeatureGateways

Five more gateways: ePayLater, Paynamics, TechProcess, emerchantpay and Ola Money

Connect them from the dashboard like any other gateway. Your integration does not change: the same POST /v1/payments works for every one.

• ePayLater, pay later for businesses in India.
• Paynamics, for payments in Philippine pesos and US dollars.
• TechProcess, in its standard and checksum-signing options. Refunds for the checksum option are made from TechProcess’s own panel.
• emerchantpay, with 26 currencies across Europe, the Middle East and beyond.
• Ola Money wallet.

FeatureGateways · API · Reconciliation

CCAvenue, ICICI and Zaakpay, payment and refund lookups, and Stripe reconciliation

A busy day across gateways, the API and the dashboard.

• New gateways: CCAvenue, ICICI Payment Gateway and Zaakpay.
• GET /v1/payments/{id} and GET /v1/refunds/{id}, so you can check a status if you missed a webhook.
• Stripe payments are checked against Stripe’s balance transactions in the daily settlement check.
• Paytm payments can use Paytm’s JS checkout.
• The hosted checkout can send customers to PhonePe, MobiKwik and Cashfree partner pages to pay.
• Every supported gateway can be managed in the dashboard, with all its credential fields, format checks, and turn off and on instead of delete.
• Billing details in the dashboard, so you can go live on your own once you have accepted the terms and connected a live gateway.

SecurityAPI · Webhooks · Dashboard

Safer defaults for live payments, keys and webhooks

Several changes that make mistakes harder and abuse more expensive.

• Live payments answer 403 until your organisation has gone live, naming what is missing: accepting the terms, billing details or a connected gateway.
• Live payments through a gateway sandbox are refused in production.
• /v1 requests are rate limited per API key and per client IP.
• Webhook endpoints are capped at 10 per organisation.
• Gateway credentials are bound to their organisation and connection.
• Saved cards (/v1/cards) are scoped to the API key’s mode.

FixPayments · Refunds

More accurate payment and refund outcomes

Fixes that keep the status you see in step with the gateway.

• A payment reported failed is captured if the gateway later proves it was paid; payment.captured follows.
• The amount a gateway reports in a status check is verified before capture.
• Payments a gateway still calls pending long after their link expired are marked failed.
• A refund Razorpay or Cashfree cannot find is reported as not found.
• A second capture of the same order is flagged as a possible duplicate charge for the ZopPay team to review.
• Validation errors answer 400 instead of 500.

ImprovementWebhooks · Checkout · Refunds

payment.failed when a checkout lapses, and one refund at a time per payment

When a customer’s checkout session expires, the payment is marked failed and payment.failed is sent. Refunds take one lock per payment across the API and the dashboard, so two refunds can’t race each other.

SecurityDashboard · Checkout

Less detail in errors, logs and sessions

Internal error detail stays out of checkout, dashboard and card responses. Email addresses stay out of sign-in and email logs. Dashboard sessions are stored under a hash of the session id.

FixRefunds

Refunds and status checks stay on the gateway that took the payment

If you switch your active gateway, earlier payments are still refunded and checked through the gateway connection that processed them.

FeatureAPI · Refunds

POST /v1/refunds for server-to-server refunds

Issue full or partial refunds from your own systems with an API key, with the same Idempotency-Key behaviour as payments.

FeatureDashboard

Sign up with email and password

Create an account and an organisation from the sign-up page, with password sign-in, forgot password and change password.

ImprovementRefunds

Refund status is checked when a gateway notification goes missing

Refunds still processing at the gateway are checked on a schedule, so a dropped gateway notification doesn’t leave them pending.

ImprovementGateways

CyberSource groundwork: authorise-then-capture and saved cards

We built CyberSource support with authorisation and capture as separate steps, and card tokens for saved cards. CyberSource is not in the dashboard’s list of gateways you can connect yet; it is marked “Coming soon”.

FeatureDashboard

Dashboard analytics and downloadable reports

Date-range summary cards, an earnings chart, top customers, and payment-method and status breakdowns. Payments and refunds download as CSV.