Payment Session and Webhooks

As payments progress through the process, you can always see its current status and with webhooks from Pay.com you'll automatically receive payment updates, so you can keep your business running smoothly.

(i) Webhooks are user defined HTTP callbacks which are triggered by specific events related to Payment or Payout objects. For example, when payment gets captured our system sees the event, collects the data, and sends it to the URL specified by you in the form of an HTTP request.
payment_session.open
The payment session was created in the system, but no action has been taken
payment_session.completed
The payment session was completed and approved and a payment
method was successfully attached, a Charge or a Hold is created
based on the payment session params
payment session.expired
The payment session has expired without a successful charge.
Expired session could have declined payment attempts
setup_session.open
The setup session was created in the system, but no action hasbeen taken
setup_session.completed
The setup session was completed and a payment method was successfully saved
charge.succeeded
The charge is approved and funds are captured
charge.failed
The payment method declined the payment request and the charge has failed
charge.refunded
A refund for the charge was created (partial or full)
charge.requires_authentication
The charge requires additional authentication before processing
charge.requires_confirmation
The charge was authenticated and requires confirmation to process
refund.succeeded
A refund for a charge was successfully created
refund.failed
The request for refund has failed
authentication_session.open
A new Authentication Session created
authentication_session.succeeded
The SCA session succeeded
refund.succeeded
A refund for a charge was successfully created
customer.created
The customer was created
customer.updated
The customer was updated
customer.default_source.changed
The customer's default source was changed
payment_attempt.succeeded
An attempt of a payment session succeeded
payment_attempt.failed
An attempt of a payment session failed
setup_attempt.succeeded
An attempt of a setup session succeeded
setup_attempt.failed
An attempt of a setup session failed
hold.requires_capture
The hold on the funds is approved and funds are awaiting capture
hold.succeeded
The hold is captured (whether fully or partially). The event will only get sent for the first capture in case of a multi-capture scenario
hold.captured
The hold is captured (whether fully or partially). The event will get sent for every capture in a multi-capture scenario
hold.failed
The payment method declined the request and the hold has failed
hold.canceled
The hold on the funds has canceled, expired or by a request of the merchant.
hold.requires_authentication
The hold requires additional authentication before processing
hold.requires_confirmation
The hold was authenticated and requires confirmation to process
payout.succeeded
The payout is approved and funds has been sent to the customer
payout.failed
The request for payout has failed
On this page