Bulk Payouts (BETA)

Create a link for direct approval of a list of outgoing transactions

Bulk Payouts lets a businesses submit multiple outbound bank transfer requests using a smart link . Use it for supplier payments, payroll, pension or provident-fund payments, and refunds.

What you need to know before you start

  • Bulk payouts uses each bank's Bulk service for processing multiple business payouts approval and execution flows.

    Different approval and execution rules may apply according to the bank account authorizations requirements.

  • Bulk payouts initiates the approval process from a specific authorizer identified with personal ID (ת.ז.) and corportate ID (ח.פ.).

  • Authorized bank signatories need to approve the batch on their bank app/website to complete the execution approval process.

  • Feezback monitors the execution approval process and sends webhook updates when the first and last assignees complete approval.

Business/Corporate accounts only

Bulk Payouts are supported for corporate accounts only.

Supported banks

Bank specific limitations
Leumi10
Hapoalim12Up to 100 payments in a bulk
Discount/Mercantile11,17Ongoing production bug on the bank
Mizrahi 20
FIBI group 14, 26, 31, 46, 52Ongoing production bug on the bank

How the Bulk Payment flow works

  1. Get a bearer token through the token generation API.
  2. Make a POST request with your payout details to the Payments API.
  3. Receive a direct-to-bank payment link in the response.
  4. Redirect the authorized signatory to approve the batch
  5. Monitor for payment status updates.

1.Create a bearer token.

  1. Create a JSON out of this payload:
{
  "sub": "sub",
  "iss": "tpp/{TPP_ID}",
  "srv": "seamless/tpp",
  "iat": 1728986260,
  "exp": 1728986860,
  "ttl": 600
}
FieldTypeRequiredDescription
substringYesSubject used for the API user path. Do not include PII if the value may appear in a URL.
issstringYesIssuer in the format tpp/{TPP_ID}.
srvstringYesUse seamless/tpp.
iatnumberYesIssued-at timestamp.
expnumberYesExpiration timestamp. Use current time plus 600 seconds.
ttlnumberYesToken TTL. Use 600.

  1. Sign the JWT with the RS512 algorithm.
    Convert the JSON from the previous step into a JWT (JSON Web Token):
    Sign the JWT with the private key that matches the public key you sent to Feezback.

    For manual JWT signing see https://www.jwt.io/.

    SettingValue
    AlgorithmRS512
    Issuer formattpp/{TPP_ID}
    Request originWhitelisted backend IP address
  2. Send this JWT to the Token Generation API:

    curl --location --request POST 'https://{ENVIRONMENT}.feezback.cloud/token' \
      --header 'Content-Type: application/json' \
      --data-raw '{
        "token": "{GENERATED_JWT_TOKEN}"
      }'

    Replace {ENVIRONMENT} with one of these values:

    EnvironmentToken endpoint
    Integrationhttps://lgs-integ01.feezback.cloud/token
    Productionhttps://lgs-prod.feezback.cloud/token
    The response token is valid for 600 seconds.
  1. The JSON response will include a token.
    Use the token value from the body for authenticating as Bearer against the TPP API, for the next 600 seconds.

2. Make a POST request with your bulk-payout details to the Payments API

Call the bulk payments API with the bearer token.

POST https://{TPP_ENVIRONMENT}-tpp.feezback.cloud/tpp/v1/users/{sub}@{tpp_id}/bulk-payments

Use the correct TPP API host:

EnvironmentTPP API host
Integrationhttps://integ01-tpp.feezback.cloud
Productionhttps://prod-tpp.feezback.cloud

Example request body:

{
  "idValue": "200200202",
  "corporateId": "511234567",
  "debtorName": "Debtor Ltd",
  "accountType": "corporate",
  "debtorAccount": "120120-001-999999",
  "remittanceInformationUnstructured": "Monthly payroll",
  "executionDate": "2026-03-03",
  "purposeCode": "SALA",
  "context": "batch-2026-03",
  "payments": [
    {
      "instructedAmount": {
        "currency": "ILS",
        "amount": "123"
      },
      "remittanceInformationUnstructured": "Salary - employee 1",
      "creditor": {
        "name": "Employee One",
        "account": "12-538-693304"
      }
    }
  ],
  "userAgreementTimestamp": "2026-02-02T11:14:05.435Z",
  "redirectSuccess": "https://success",
  "redirectFailure": "https://failure",
  "redirectNotComplete": "https://notComplete",
  "redirectNotConclusive": "https://notConclusive"
}

Request fields

Field
Type
Required
Notes
idValue
string
Yes
Authorized signatory identifier.
corporateId
string
Yes
Debtor's corporate identifier. Must be a valid business number, contain 9 digits, and start with 51. The API validates the number, including in tests.
debtorName
string
Yes
Debtor business name.
accountType
string
Yes
Use business or corporate.
debtorAccount
string
Yes
Debtor account funding the payout.
remittanceInformationUnstructured
string
Yes
Batch-level remittance information.
executionDate
string
No
Optional future execution date. Use YYYY-MM-DD format.
purposeCode
string
Conditional
Use SALA for salary payments only.
context
string
Recommended
Client context returned in status updates.
payments
array
Yes
List of outbound payments in the batch.
userAgreementTimestamp
string
Yes
Timestamp of the user’s agreement in ISO 8601 format.
redirectSuccess
string
Yes
Redirect URL for successful completion.
redirectFailure
string
Yes
Redirect URL for failure.
redirectNotComplete
string
Yes
Redirect URL when the signer does not complete the flow.
redirectNotConclusive
string
Yes
Redirect URL when the result is not conclusive.

Payment item fields

Field
Type
Required
Notes
payments[].instructedAmount.currency
string
Yes
Payment currency. Use ILS for the documented ILS flow.
payments[].instructedAmount.amount
string
Yes
Payment amount.
payments[].remittanceInformationUnstructured
string
Yes
Payment-level remittance information.
payments[].creditor.name
string
Yes
Receiver name.
payments[].creditor.account
string
Yes
Receiver account. Must be unique within the batch. Multiple payments to the same creditor account in one batch are not supported and cause the batch to be rejected.

Limits and rules

RuleDetails
Account typeUse business or corporate.
Corporate IDcorporateId must be a valid debtor business number, contain 9 digits, and start with 51. Use a valid business number in tests as well.
Unique creditor accountsEach payment must use a different creditor account. A batch containing multiple payments to the same creditor account is rejected.
Salary paymentsUse purposeCode: "SALA" only for salary payments.
Future executionUse executionDate for optional future-dated execution.
Hapoalim batch sizeMaximum 100 items per bulk payment.
Production creditor accountsCreditor accounts may need to be approved before production use.

Response — 201 Created

When the bulk payment request is created successfully, the API returns HTTP 201 with a direct-to-bank link and a payment identifier.

{
  "redirectUri": "https://example-bank-redirect.example/authorize-payment",
  "paymentId": "0f2aee50-dd9f-4bee-9583-1c7809c4f933",
  "aspspIssues": []
}
FieldTypeDescription
redirectUristringDirect link to the bank's website or mobile app. Redirect the authorized signatory to this URL to approve the batch. The URL above is illustrative.
paymentIdstringUnique identifier for the transaction, generated by Feezback. Store it to identify the bulk payment when troubleshooting.
aspspIssuesarray of objectsActive service issues reported for the debtor's bank. An empty array means no active issues are reported.

Creating the request does not mean the batch has been approved or executed. Monitor payment status updates for the outcome.

Statuses

Bulk payments progress through bank statuses.

RCVD → PATC / PART → ACTC / ACWC / RJCT / CANC
StatusMeaning
RCVDInitial request received.
PATCIn progress.
PARTPartially processed or partially authorized.
ACTCFinal successful status.
ACWCFinal successful status with change.
RJCTFinal unsuccessful status: rejected.
CANCFinal unsuccessful status: cancelled.

Common error codes

HTTPCodeMeaningAction
400INVALID_PAYMENT_PAYLOADA field is missing or invalid. The offending field is named in the error message.Fix the payload and resubmit.
400IBAN_IS_NOT_WHITELISTEDCreditor account is not approved in production.Contact Feezback to whitelist the account.
424ASPSP_ERRORThe request passed Feezback validation but was rejected by the bank.Contact Feezback with the paymentId and exact timestamp.
500PAYMENT_REQUEST_FAILEDThe payment could not be created.Retry. Escalate if persistent.

Testing outcomes

Use the 5-digit test account 12345 with these PSU IDs to test bulk payout outcomes.

Send a valid debtor business number in corporateId for every test. The API validates this number; matching the 9-digit format and 51 prefix alone is not sufficient.

Test PSU IDResult
200200202Accepted — technical validation
998814644Rejected
320634389Partially authorized



Did this page help you?