Payments Webhook

For general webhook mechanics (response requirements, security, IP whitelisting, troubleshooting), see Webhooks - Async Updates. This page covers the webhook event fired for FAST and Seamless payment requests.

For general webhook mechanics (response requirements, security, IP whitelisting, troubleshooting),

see Webhooks - Async Updates or Webhook Security

Event: PaymentStatusChanged

Fired on every status transition of a payment request (single or recurring/הו"ק).

{
  "timestamp": "2021-03-04T12:26:32.212913+00:00",
  "event": "PaymentStatusChanged",
  "payload": { ... }
}

Payload fields

FieldTypeDescriptionExample
userStringUser identifier"123456782@tppName"
paymentRequestStringUnique payment UUID"9739700b-..."
psuIdStringPayer identifier"123456782"
requestedAmountStringAmount requested"1.00"
finalAmountObject / falseFinal settled amount. false for periodic/direct-debit payments (see note below){"amount": "1.00", "currency": "ILS"}
aspspCodeStringBank code"20"
accountNumberStringIBAN / account number"IL7902..."
psuMessageString | nullReference number"002115"
referenceNumberString | nullReference number"002115"
contextStringThe context you sent in the original JWT"tx-001"
transferTypeString"masav" | "fp" | "zahav"
accountTypeString"PRIVATE" | "BUSINESS" | "CORPORATE"
corporateIdNumberCorporate ID, if relevant515555555
currentStatusStringSee status table below
previousStatusString | nullnull if this is the first status update
recurringBooleanOnly sent for periodic paymentstrue
startDateISO dateOnly sent for periodic payments"2025-12-12"
tppStringYour organization identifier"tppID"

⚠️ Do not validate against a strict schema. The bank may return additional fields inside payload that aren't listed here — parse only what you need.

Note on finalAmount in recurring payments: while recurring: true, finalAmount comes back as false (not an object) because the final amount isn't known yet. Don't rely on it before a terminal status is reached.


Statuses

Status
Definition
Masav
FP
Zahav
Comment
received
Payment initiation request is received by the bank.
First
status
First
status
First
status
Triggers when the user is redirected to the bank.
rejected
Payment initiation has been rejected.
When we get this status, the user is redirected to Feezbacl/Your rejection url.
expired
The timeout for the RCVD payment has expired.
When we get this status, the user is redirected to Feezback/Your expiration url.
partially
Accepted
Technical
Correct
The transaction requires multiple authentications, where some but not yet all have been performed.
Mostly relevant for corporate accounts where approval process required. This status means the transaction awaits further approval by other account assignees. After the transaction is approved by the rest of the assignees, the status will change to acceptedTechnicalValidation.
accepted
Funds
Checked
Preceding check of technical validation and customer profile was successful, and an automatic funds check was positive.
X
Last status
X
accepted
Technical
Validation
Transaction approved by the debtor bank and will be executed by the end of the current business day.
Last status
X
X
The debtor has the option to cancel the transfer on the bank channels until the transfer is executed. If approved after hours, it will be assigned to the next business day.
accepted
With
Change
Transaction approved by the debtor bank and will be executed by the end of the current business day, with minor changes like shortening the description of the transfer.
Last status
X
X
The debtor has the option to cancel the transfer on the bank channels until the transfer is executed. If approved after hours, it will be assigned to the next business day.
accepted
Settlement
In
Process
Transaction approved by the debtor bank and will be executed immediately.
X
Last status
X
accepted
Settlement
Completed
Transfer approved and executed by the debtor bank immediately.
X
Last status
X
Settlement of the transaction has been executed and booked on the debtor account.
accepted
Settlement
Completed
Creditor
Account
Settlement on the creditor's account has been completed.
X
X
Last status
Settlement of the transaction has been executed and booked on the creditor account (relevant only for Zahav payments).
executed
Funds received in the creditor account.
Last status
Last status
Last status
Relevant for the "Match" service. For customers that enabled tracking transactions in the creditor account, this will always be the last status, overriding other final statuses.
cancelled
The user cancelled the payment.
Last status
X
X
For periodic payments only. Will be received if the user cancelled the periodic order via the bank channels (not supported on FIBI banks).

Common questions

QuestionAnswer
previousStatus is nullThis is the first status update for this payment
finalAmount: false on a recurring paymentNormal — final amount isn't known until a terminal status
Did acceptedTechnicalValidation succeed?Yes (Masav/Zahav) — will execute by end of business day
Not receiving this webhookCheck IP whitelisting — see Webhooks & IP Whitelisting

Did this page help you?