Bulk Payouts Webhook

For general webhook mechanics (response requirements, security, IP whitelisting, troubleshooting), see Webhooks - Async Updates or Webhook Security.

ℹ️ This fires under the same PaymentStatusChanged event as the other payment webhooks (see Webhooks Events Catalog) — Bulk Payouts just has its own payload shape, documented below. The Presence column tells you whether a field is always sent ("Fixed") or only sent under certain conditions ("Optional").

Bulk payment status webhook

Payload fields

Field	Presence	Description
`user`	Fixed	`sub@tpp`
`paymentRequest`	Fixed	Feezback-generated UUID
`aspspCode`	Fixed	Bank code
`psuId`	Fixed	Authorized signatory ID
`psuCorporateId`	Fixed	Corporate ID (ח.פ.)
`debtorName`	Fixed	Paying organization's name
`bulkIdentifier`	Fixed	Bulk batch identifier
`bulkDescription`	Optional	If provided in the JWT configuration.
`executionDate`	Fixed	Execution date
`requestedAmount`	Fixed	Total amount
`psuMessage`	Fixed (null if the bank did not send any or not final status)	Reference number (אסמכתא)
`referenceNumber`	Optional — an additional reference value the bank may optionally return, may include other bank-specific references	Additional bank reference (optional, bank-dependent)
`transferType`	Fixed	`masav` / `fp`
`currentStatus`	Fixed	See status list below
`previousStatus`	Fixed (nullable — `null` if first update)
`tpp`	Fixed	Your organization identifier
`resourceId`	Fixed	Bank-side resource identifier
`purposeCode`	Fixed — field always present; `null` if not available.	ISO 20022 purpose code set via the JWT.
`payments`	Fixed	Array of underlying payment legs — see fields below
`paymentsCount`	Fixed	Number of entries in `payments`

payments[] object fields:

Field	Description
`amount`	Amount of this payment leg
`currency`	Currency code
`creditorAccount`	Creditor's account number / IBAN
`creditorAccountType`	Creditor account type
`description`	Description of this payment leg

⚠️ Do not validate against a strict schema. Additional fields may be present — parse only what you need.

Statuses

Initial: RCVD
Intermediate: PATC (partially approved, needs further approval), PART (some payments received)
Terminal: ACTC (AcceptedTechnicalCorrect ✅), ACWC (AcceptedWithChange ✅), RJCT (Rejected ❌), CANC (Cancelled ❌)

Related error codes (payment creation, not webhook)

Status	Error Code	Meaning
400	`INVALID_PAYMENT_PAYLOAD`	Missing or invalid field
400	`IBAN_IS_NOT_WHITELISTED`	Creditor account not whitelisted
424	`ASPSP_ERROR`	Passed Feezback validation but the bank rejected it — contact Feezback with the `paymentId` and exact time
500	`PAYMENT_REQUEST_FAILED`	Failed to create the payment

Testing (Mock Bank)

Create a bulk payment without debtorAccount in the request.
Choose MockBank on the Feezback screens.
Enter a 5-digit account number: 12345.

Test ID (`psuId`)	Result
`200200202`	acceptedTechnicalValidation ✅
`998814644`	Rejected ❌
`320634389`	Partially Authorized

Bulk payment status webhook

Payload fields

Field

Presence

Description

user

Fixed

sub@tpp

paymentRequest

Fixed

Feezback-generated UUID

aspspCode

Fixed

Bank code

psuId

Fixed

Authorized signatory ID

psuCorporateId

Fixed

Corporate ID (ח.פ.)

debtorName

Fixed

Paying organization's name

bulkIdentifier

Fixed

Bulk batch identifier

bulkDescription

Optional

If provided in the JWT configuration.

executionDate

Fixed

Execution date

requestedAmount

Fixed

Total amount

psuMessage

Fixed (null if the bank did not send any or not final status)

Reference number (אסמכתא)

referenceNumber

Optional — an additional reference value the bank may optionally return, may include other bank-specific references

Additional bank reference (optional, bank-dependent)

transferType

Fixed

masav / fp

currentStatus

Fixed

See status list below

previousStatus

Fixed (nullable — null if first update)

tpp

Fixed

Your organization identifier

resourceId

Fixed

Bank-side resource identifier

purposeCode

Fixed — field always present; null if not available.

ISO 20022 purpose code set via the JWT.

payments

Fixed

Array of underlying payment legs — see fields below

paymentsCount

Fixed

Number of entries in payments

amount

Amount of this payment leg

currency

Currency code

creditorAccount

Creditor's account number / IBAN

creditorAccountType

Creditor account type

description

Description of this payment leg

Statuses

Related error codes (payment creation, not webhook)

Testing (Mock Bank)

`user`

`sub@tpp`

`paymentRequest`

`aspspCode`

`psuId`

`psuCorporateId`

`debtorName`

`bulkIdentifier`

`bulkDescription`

`executionDate`

`requestedAmount`

`psuMessage`

`referenceNumber`

`transferType`

`masav` / `fp`

`currentStatus`

`previousStatus`

Fixed (nullable — `null` if first update)

`tpp`

`resourceId`

`purposeCode`

Fixed — field always present; `null` if not available.

`payments`

`paymentsCount`

Number of entries in `payments`

`amount`

`currency`

`creditorAccount`

`creditorAccountType`

`description`