CASH WEBHOOK

Kushki can send webhook events that notify your application any time one of the following events happens:

  1. When your authorization is necessary to collect the payment (pre-authorization)
  2. When the client made the payment (payment notification)

Here’s what a complete payload looks like when it’s delivered to a Cash webhook:

Method: POST

headers
object
X-Kushki-Key
string
X-Kushki-Signature
string

For payment notification only

X-Kushki-Id
integer
body
object
ticketNumber
string
token
string
totalAmount
number
amount
object
iva
number
subtotalIva
number
subtotalIva0
number
extraTaxes
object
currency
string
created
number
expiration
number
status
string

For pre-authorization event: “initializedTransaction” or “expiredTransaction”. For payment notification event: “approvedTransaction” or “declinedTransaction”

identification
string
name
string
lastName
string
merchantId
string
merchantName
string
processorName
string

When you receive notifications for the pre-authorization event, a response from your side is needed in order to collect the payment.

RESPONSES:

200
body
The payment has authorization to be collected
null
400 or 500
body
The payment can not be collected
object
code
string

Allowed values: KSH1, KSH2 or KSH3

example: KSH2
default: KSH1
message
string

Allowed values: NOTFOUND, PAID, EXPIRED

example: PAID
default: NOTFOUND