EPSPayment operations

Hosted checkout, ecommerce, and API paths

Connect payment state to the system that fulfills the order

Choose an EPS integration based on what your website, app, finance team, and support operation must know after the customer pays.

Discuss an integration Review security controls
The simplest reliable path wins.

Hosted checkout can reduce sensitive frontend work. Server callbacks become important when fulfillment cannot rely on a browser return alone.

Three routes

Match integration depth to operating risk

Every route should produce a reliable order reference, clear customer return, server-verified payment state, and testable failure handling.

Hosted checkout

Open a controlled payment page

Create a session, send the customer to checkout, return them to the merchant site, and verify the final state on the server.

Ecommerce

Connect the order lifecycle

Review Shopify, WooCommerce, or another commerce platform for checkout placement, order updates, refunds, and production approval.

API

Control platform workflows

Create sessions, query status, receive callbacks, and connect payment evidence to an internal order, ERP, or finance system.

Implementation contract

Design around states, not a single “success” page

A browser return can be interrupted. A customer can close the tab. A provider can report a pending state. Your server-side integration should be able to ask what happened.

  • CreatePass the amount, currency, order reference, return URL, and callback URL.
  • VerifyConfirm that the transaction belongs to the expected order and amount.
  • UpdateHandle approved, pending, failed, declined, and refunded outcomes without duplicate fulfillment.
  • ReconcileKeep the gateway reference alongside the merchant order and settlement record.
Illustrative callbackEPS → merchant server
{
  "event": "payment.updated",
  "order_reference": "ORDER-1042",
  "gateway_reference": "EPS-DEMO-8821",
  "status": "APPROVED",
  "amount": "12500.00",
  "currency": "PKR"
}
Go-live gate

Test the failure path before the first live payment

Production readiness should cover duplicate callbacks, wrong amounts, abandoned checkout, delayed status, rejected payment, refunds, missing credentials, and recovery after a timeout.

Plan technical onboarding
  1. 1
    Sandbox evidence

    Capture test references for approved, pending, failed, and refunded flows.

  2. 2
    Idempotent fulfillment

    Ensure the same event cannot fulfill an order twice.

  3. 3
    Production separation

    Keep live credentials and callback endpoints out of test systems.