Capture

Capture an authorized card payment to finalize the charge and settle funds.

Use this API when a payment was initiated with capture: "false" (onetime, tokenization, or direct charge) and is currently Authorized.

---

Endpoint

Method	POST
Path	/cards/capture
Sandbox	https://sandbox.simpaisa.com/cards/capture

---

Headers

Header	Value
client-id	Your Client ID (e.g. YOUR_CLIENT_ID)
Content-Type	application/json
merchantId	Your unique merchant ID (e.g. YOUR_MERCHANT_ID)
mode	cards
region	PK
version	V5

---

Request Body

Parameter	Required	Description
request.reference	Yes	Reference of the authorized transaction to capture
signature	Yes	RSA signature of the request object

---

Response Body

Parameter	Description
response.id	Unique payment ID
response.action_id	Unique action ID for the capture
response.approved	Whether the capture is approved
response.status	Captured on success; Declined on rejection
response.response_code	Outcome code — 10000 on success. 40025 if the reference belongs to a zero-amount tokenization transaction
response.response_summary	Human-readable outcome
response.transaction_state.CAPTURE_STATUS	SUCCESS on success — absent on decline
response.source	Source ID/type
response.reference	Reference from the request
response.transaction_id	Simpaisa transaction ID
signature	RSA signature of the response body

---

Samples

Successful Capture

Request

curl --location 'https://sandbox.simpaisa.com/cards/capture' \
--header 'client-id: YOUR_CLIENT_ID' \
--header 'merchantId: YOUR_MERCHANT_ID' \
--header 'mode: cards' \
--header 'region: PK' \
--header 'version: V5' \
--header 'Content-Type: application/json' \
--data-raw '{
  "request": { "reference": "h388-1782917244521" },
  "signature": "YOUR_SIGNATURE"
}'

Response

{
  "response": {
    "id": "pay_28f3d06b5e2445858994eaa032",
    "action_id": "act_7f56443d348048c0a1989ab39a",
    "approved": "true",
    "status": "Captured",
    "response_code": "10000",
    "response_summary": "Approved",
    "transaction_state": {
      "CAPTURE_STATUS": "SUCCESS"
    },
    "source": {
      "id": "src_841d885af66f47a3b0ec69bf63",
      "type": "CARD"
    },
    "processed_on": "2026-07-01T14:49:17Z",
    "reference": "h388-1782917244521",
    "transaction_id": "3282"
  },
  "signature": "YOUR_SIGNATURE"
}

This behavior is unchanged for Tokenization (non-zero amount) transactions authorized with capture: "false" — capturing them succeeds the same way, and c_token remains retrievable via Inquiry afterward.

Zero-Amount Tokenization (Rejected)

Calling Capture against a reference created via zero-amount tokenization (payment_type: "tokenization", amount: "0.00") is rejected:

Request

curl --location 'https://sandbox.simpaisa.com/cards/capture' \
--header 'client-id: YOUR_CLIENT_ID' \
--header 'merchantId: YOUR_MERCHANT_ID' \
--header 'mode: cards' \
--header 'region: PK' \
--header 'version: V5' \
--header 'Content-Type: application/json' \
--data-raw '{
  "request": { "reference": "tok-c2-1782917563029" },
  "signature": "YOUR_SIGNATURE"
}'

Response

{
  "response": {
    "id": "pay_e6a31de6ef6e4bd28d5d84b4db",
    "action_id": "act_defa854af940486cb079196f4b",
    "approved": "false",
    "status": "Declined",
    "response_code": "40025",
    "response_summary": "Capture is not applicable for zero-amount tokenization.",
    "processed_on": "2026-07-01T14:54:02Z",
    "reference": "tok-c2-1782917563029",
    "transaction_id": "3284"
  },
  "signature": "YOUR_SIGNATURE"
}

Postback After Capture

See Postbacks for the asynchronous notification sent after capture, or use Inquiry to confirm status directly.