Segpay
Adapter 0.1.0, documentation reviewed 2026-10-25. Overall status: limited.
Capabilities
| Error decoding | limited |
| API response parsing | unsupported |
| Webhook / notification parsing | limited |
| Timeline | limited |
| Event correlation | supported |
| Diagnostic rules | limited |
Supported input
| Format | Description | Status |
|---|---|---|
segpay.processing.transaction | Processing transaction postback with default key names (trantype, action, stage, approved, purchaseid, tranid) | limited |
segpay.processing.member | Processing member management postbacks (Inquiry/Probe, Enable, Disable, Cancel, Reactivation) | limited |
segpay.processing.paypal_dispute | Processing PayPal Dispute postback (disputeid, disputestage, currentstatus) | limited |
segpay.gateway.notification | Gateway Event Notification (EventCode, SubEventTypeID, TransactionID, SubscriberID, ResponseCode) | limited |
segpay.processing.custom_postback | Processing postbacks with merchant-chosen key names (recognized, not analyzed) | unsupported |
segpay.gateway.xml | Gateway XML API responses (authresponse, creditresponse, rebillresponse, ...) | unsupported |
segpay.srs | SRS reporting and admin web service responses (.NET DataSet XML, plain strings) | unsupported |
segpay.gateway.express_stats | Gateway Express Stats XML | unsupported |
segpay.membership_upgrade | Membership Upgrade API JSON/XML responses | unsupported |
segpay.oneclick | One-Click web service responses | unsupported |
segpay.mpi.v4 | MPI V4 (3DS2) browser callback objects | unsupported |
Notification delivery
- Repeated deliveries are recognized by Processing: tranid + trantype + action + stage + approved (not for Stand-In postbacks); Gateway: TransactionID + EventCode (Segpay documents no event id); Segpay documents that notifications can be delivered more than once.
- Delivery order: not documented by the provider.
- Make postback handling idempotent per tranid and result (Processing) or TransactionID and EventCode (Gateway). Do not treat a Stand-In decline as a repeat of the temporary approval: it reuses the same tranid and purchaseid.
Known limitations
- Processing and Gateway are separate products with separate formats; they are analyzed as separate input families and their identifiers are never mixed.
- Default Processing postback key names are not tabulated by Segpay; they are taken from published screenshots. Postbacks that use merchant-chosen key names are recognized from value shapes but not analyzed.
- Segpay publishes no full example of the Inquiry, Enable, Disable, Cancellation or Reactivation postbacks; their parsing follows the token tables only, and reason code values in them are not documented, so they are shown as raw codes.
- No signature, HMAC or event id is documented for Processing postbacks or Gateway notifications. A pasted postback is never treated as verified, and the HTTP credentials Segpay supports are not part of the payload.
- Delivery keys use documented identifiers only: tranid + trantype + action + stage + approved for transaction postbacks, TransactionID + EventCode for Gateway notifications. Member management and PayPal dispute postbacks get no delivery key. Whether processingtime changes on a retry is not documented, so it is not part of the key.
- A Stand-In decline reuses the temporary approval's tranid and purchaseid. Stand-In postbacks (standin=1) never get a delivery key, so they are never reported as duplicates; a temporary approval is shown as pending, not as a final approval.
- The authcode format is not specified. It is decoded only when its prefix is a documented fraud code (F4xx, V30xx), an Instant Conversion / One-Click error (ERR301-ERR310) or a scheme code in Segpay's Visa categories or Mastercard buckets; anything else is reported as unknown. The rest of authcode can contain the blocked email or other customer data and is never copied.
- Segpay's Visa category 4 (all other codes, reattempts allowed) is not applied automatically, because the authcode prefix is not guaranteed to be an issuer code.
- Mastercard Merchant Advice Codes, Visa recurring cancellation codes and MPI V4 named errors are catalogued, but no supported Segpay payload field that carries them is documented.
- The Processing rebill retry schedule, the final failure signal after retries and the Gateway Flex Rebill rules are not documented; a declined rebill does not show whether Segpay will retry it.
- Gateway XML API responses, Express Stats, SRS reports and admin responses are XML or plain strings, which PandaPayLens core does not parse; they are not recognized. Membership Upgrade and One-Click responses are undocumented or malformed in the documentation and not analyzed.
- Postback timestamps (transtime, PayPal dispute dates, Gateway Timestamp) are read as GMT as Segpay states; whether the GMT STANDARD TIME label follows UK daylight saving is not documented, so times may be off by one hour in summer.
- Events are grouped by purchaseid, tranid and relatedtranid (Processing) and by TransactionID, OriginalTransactionID, RefundTransactionID and SubscriberID (Gateway). A purchase groups every billing cycle of a subscription. A recurring One-Click purchase gets a new purchaseid and is not linked to the original. Gateway SubscriberID is documented as unique per customer, so purchases of one customer may share a group.
- Gateway S events mean either a single sale or the settlement of an earlier authorization; the payload does not say which. A Gateway rebill (R) is treated as approved unless its ResponseCode says otherwise.
- Amounts without a currency code (Gateway notifications without CurrencyCode, PayPal dispute transamount) are shown as attributes only, not as minor-unit amounts.
- Test transactions (TESTTRANS / TESTRANS = 1) are flagged; Segpay does not support rebills, refunds or voids in test mode.
- Orchestration (merchant pooling, smart routing) applies to the Gateway product only.
Examples
- Segpay: rebill declined: A form-encoded postback for a failed recurring charge.
- Segpay: Stand-In decline: A Stand-In approval followed by a decline that reuses the same ids; not treated as a duplicate.
- Segpay: PayPal dispute postback: A dispute postback linked to the original purchase.
Provider documentation
- Processing API: Postbacks
- Processing API: Postback parameters
- Transaction Postback Matrix
- Processing API: Error codes (fraud, Instant Conversion, One-Click)
- Merchant Portal: Manage postbacks
- PayPal Dispute configuration
- Stand-In
- Gateway Integration Guide (event codes, sub event types, response codes)
- Merchant Advice & Response Codes
- 3D Secure MPI V4
- Gateway hosted pay page signed requests
PandaPayLens is not affiliated with Segpay. Pasted notifications are never treated as verified: PandaPayLens does not check webhook signatures.