Webhooks
Paysight provides a webhook-based integration for clients to receive near real-time batched notifications for billing and subscription events.
Configuration
Clients can configure individual webhook URLs per event type at Paysight Account Settings
Available Event Types
Event Type | Description |
---|---|
New Transaction | Triggered when a new billing event occurs (authorize, sale, refund, chargeback, or alert). |
Updated Transaction | Triggered when an existing authorized transaction is captured or cancelled. The status , statusId and completed fields will be updated. Please note: You will not receive an updated transaction for transactions that are refunded / charged back. You will receive these in the New Transaction event webhook as they are a separate transaction but can be linked back to the original tranaction (see above) |
New Subscription | Triggered when a new customer subscription is created. |
Cancelled Subscription | Triggered when a subscription is cancelled. |
Chargeback Alert | Raw unmatched chargeback alerts from mitigation provider. |
Chargeback | Raw unmatched chargeback records reported against the client. |
For New Transaction event type, the important properties are:
transactionId
orderId
originalTransactionId
- if the transaction is a Refund, Chargeback Alert or Chargeback then the OriginalTranactionId will be provided which references the tranaction that was refunded/charged back These transactions can be identfied via the applicationId property listed below and will have a negativeamount
value:- Refund -
applicationId
= 200 - Chargeback -
applicationId
= 201 - Chargeback Alert -
applicationId
= 202
- Refund -
Delivery & Performance
- Batch Delivery: Webhooks are sent as arrays of event objects.
- Response Time: Your server must respond with HTTP 200 OK within 2 seconds.
- No Inline Processing: Please queue events for asynchronous processing.
Payload Structure
New Transaction / Updated Transaction
Field Descriptions for Transaction Events
NMI/Payon/EmerchantPay etc
Paysight’s unique identifier for the transaction (also referred to as messageId)
The unique order refrerence to which the transaction relates. This will match the orderId returned in the original widget/card submit response
Timestamp in GMT when transaction was initiated
User Email address
Indicates if transaction was simulated (sandbox=true) or real (sandbox=false)
Paysight’s unique identifier of the transaction type
Status of the transaction
Paysight’s unique identifier of the status of the transaction
Indicates if the billing event was successful (fully captured funds or successful refund etc)
Timestamp in GMT when transaction was finalized
Transaction currency (e.g ‘USD’)
Transaction amount (e.g 9.99)
Merchant Account Identifier
Merchant Account Descriptor
Paysight Customer Id
Gateway Authorization code
Gateway Transaction Id
Customer First Name
Customer Last Name
Card Bin (first 6 digits)
Card Last 4 digits
Indicates if Transaction has been refunded
Indicates if Transaction is refundable
Indicates if Transaction has a related Charegack alert
Indicates if Transaction was charged back
Paysight Transaction Type
Paysight Transaction Type 2 (classifies transactions in a similar way to above with some specific differences. Speak to support team for more info)
Identifier for above. Speak to support team for more info)
Shopify Store Id (if applicable)
Shopify Store Name (if applicable)
Shopify Store Domain (if applicable)
Shopify Store Root Domain (if applicable)
Paysight Identifier for Merchant Account
MID Name/Title/Description
Merchant Account Company Identifier
Merchant Account Company
Paysight Tenant Identifier (ClientId)
Paysight Subscription Identifier
Paysight Subscription Name
Identifier for Refund Source (if applicable)
Identifier for Alert Type (if applicable)
Identifier for Alert Source (if applicable)
Unique identifier of Card Submit event
Chargeback Mitigation Provider (e.g Kount)
Chargeback Alert Type, e.g RDR, Ethoca, CDRN
Source of Refund (if applicable) e.g Alert Related, Customer Service etc
Country Code associated with issuing Bin
Country code associated with user IP address (from original session)
Paysight unique identifier for Client’s campaign
Client’s campaign
Paysight unique identifier for Client’s traffic source/affiliate
Client’s traffic source/affilia
Paysight unique identifier for Product, which is the entry point and determines how a user should be handled
The Product contains the settings that determine how a user is handled/charged when they interact with Paysight via the Payment Widget / Card Submit API
Paysight Billing Cycle. Indicates the number of payments that the user has made on the applicable subscription. e.g 4 = User has made 3 previous payments before this one
attempt=1 is the first natural attempt. attempt=2 is the first retry. attempt=3 is the 2nd retry etc.
For refunds, chargebacks and chargeback alerts this is the reference to related transaction
New Subscription / Cancelled Subscription
Field Descriptions for Subscription Events
Paysight Tenant Identifier (ClientId)
Identifier for Merchant Account Company
Merchant Account Company
Merchant Account Identifier
MID Descriptor
Unique identifier for the customer’s specific subscription
Unique identifier for the customer
Timestamp in GMT when the user was subscribed
Timestamp in GMT when the user unsubscribed/cancelled
The unique order refrerence to which the transaction relates. This will match the orderId returned in the original widget/card submit response
True if the user has not yet cancelled or been unsubscribed
Unique identifier for the unsubscribe event (null if user has not yet unsubscribed)
Customer Email
Unique identifier for the Subscription (service) on Paysight
Name of the Subscription (service) on Paysight
Paysight unique identifier for Product, which is the entry point and determines how a user should be handled
The Product contains the settings that determine how a user is handled/charged when they interact with Paysight via the Payment Widget / Card Submit API
True if Paysight is no longer attempting to bill the customer (this will happen after retry strategies have been exhausted or specifc hard declines)
Indicates if user was added to the subscription as a cross sale (from another subscription)
Indicates how the user was unsubscribed. Values are:
ChargebackAlert
CustomerService
Chargeback Alert
The Chargeback Alert event webhook will provide a uniform feed of all chargeback alerts. This is still under development
Chargeback
The Chargeback event webhook will provide a uniform feed of all chargeback alerts. This is still under development
Best Practices
- Always respond with
HTTP 200 OK
within 2 seconds. - Do not process payloads inline—queue them for background processing.
- Log webhook events and delivery statuses.