Payment lifecycleStatement matched
Merchant developer sees why payment.captured is safe to fulfill: capture, receipt, and signed webhook evidence share the same lifecycle.
statement matchedCheckoutcs_school_2026_001
Paymentpay_scenario_001
Amount125,000 IQD
ReceiptEP-RCPT-2026-00041
Statementset_2026_06_15_iqd
Checkout session createdHosted checkout receives the merchant link, amount, locked reference, and allowed payment methods.cs_school_2026_001
createdIssuer authentication requiredCustomer can still pay as guest; issuer OTP must pass before capture.auth_school_2026_001
authentication requiredAuthentication approvedAuthentication evidence is retained for risk, support, and dispute work.acs_school_2026_001
authenticatedPayment authorizedThe selected IQD card route confirms the amount before capture.route_live_cards_iqd
authorizedCapture postedGross, fee, merchant net, and reserve hold become immutable ledger evidence.mov_payment_capture_001
capturedReceipt issuedCustomer receives an immutable receipt without needing an Epara account.EP-RCPT-2026-00041
receipt issuedMerchant webhook deliveredMerchant endpoint receives signed payment.captured notification.evt_payment_captured_001
webhook deliveredStatement matchedHosted checkout capture appears in merchant statement and operator reconciliation.set_2026_06_15_iqd
statement matchedPayout pendingEligible merchant balance waits for provider payout confirmation.po_school_2026_001
pendingFailed, expired, and cancelled checkout sessions never create fee, reserve, receipt, or payout lines.
Webhook fulfillment handoffCan the merchant trust this event?
The webhook is not just a log: it tells the merchant backend which student reference can be marked paid after signature verification.
int_handoff_school_2026_001 fulfilledPaymentpay_scenario_001
Webhookevt_payment_captured_001
Credentialcred_demo_live_01
Fulfillmentfulfill_school_fee_reference_00041
Webhook eventevt_payment_captured_001
deliveredpayment.captured delivered to merchant endpoint.
Payload previewJSON
{
"id": "evt_payment_captured_001",
"type": "payment.captured",
"livemode": true,
"data": {
"object": {
"id": "pay_scenario_001",
"amount": 125000,
"currency": "IQD",
"status": "captured",
"reference": "SCH-2026-00041",
"payment_link": "plink_school_2026",
"checkout_session": "cs_school_2026_001",
"receipt": "rcpt_scenario_001"
}
}
} Signature and linked objects
Payload hashsha256:8f1d6c0f0f9f1d1a6a7f9c93dd4f0b1d55fb6c4d4f2e2f0a91c1c6f5e8a3a102
Noncenonce_school_2026_001
Paymentpay_scenario_001
Receiptrcpt_scenario_001
Why this matters
Merchant developerFulfillment triggerThe merchant system can fulfill the school fee order after verifying the signature and payment status.
Epara operationsDelivery evidenceSupport can prove the event was delivered with a retained payload hash, nonce, attempt, and response code.
Finance125,000 IQDThe webhook does not move money; it reports the payment state after ledger and provider capture evidence exists.