Registering External Mandates
רישום הרשאה לחיוב חשבון שהוקמה עצמאית מול הבנק (ולא דרך פיזבק) - Register a direct debit mandate your customer approved at their bank, then charge it by customerId
Some customers can't approve a Direct Debit Mandate through Feezback: their account has no digital permissions, they have no digital bank identification, or they just prefer to do it directly with their bank. These customers can still approve the mandate directly with their bank. A mandate created this way is an external mandate.
This page explains how to register an external mandate with Feezback and how to charge against it. Once registered, you charge it with only the customerId, exactly as you do for a mandate established through Feezback.
Prerequisites
- Your
organizationCodeis whitelisted with Feezback. Contact your integration contact to confirm. - Your customer approved the mandate with their bank, in your organization's name. Keep the reference documentation the customer gives you. Feezback does not verify the mandate with the bank at the time you register it.
- You have a
customerIdfor the debtor: your own identifier for this customer. You choose it when you register.
How it works
- Your customer approves the mandate at their bank.
- You call the registration endpoint with the
customerId, the debtor's account, and the debtor's ID details. - Feezback registers the mandate with status
valid, linked to yourcustomerId. - You charge the mandate by sending only the
customerIdin your charge lines. Feezback adds the debtor account and ID details.
Registering an external mandate
Environments
1. Create a token. See Configuring Environments & Security for token issuance:
| Action | Integration URL | Production URL |
|---|---|---|
| Generate a bearer token | https://lgs-integ01.feezback.cloud/token | https://lgs-prod.feezback.cloud/token |
2. Send the request with the token.
| Environment | Endpoint |
|---|---|
| Integration | https://integ01-tpp.feezback.cloud/tpp/v1/debits/registrations |
| Production | https://prod-tpp.feezback.cloud/tpp/v1/debits/registrations |
Method: POST · Auth: Bearer token
Request
{
"organizationCode": "22245802",
"customerId": "8834215",
"debtorName": "שם לקוח",
"debtorAccount": "10-123-1234567",
"debtorPsuId": "512222222",
}| Field | Required | Description |
|---|---|---|
organizationCode | Yes | Your Masav creditor organization code (8 digits). Must be whitelisted with Feezback. |
customerId | Yes | Your identifier for the debtor. You will use it to charge this mandate. |
| debtorName | optional | Your customer name. |
debtorAccount | Yes | The debtor's account number, in the format bank-branch-account, for example 10-123-1234567. |
debtorPsuId | Yes | Business number (ח.פ.) or Israeli government ID of the account holder |
Response
When you register an external mandate, the HTTP response code indicates the outcome:
A request with an organizationCode that is not whitelisted for you is rejected. Other standard HTTP error codes include 401, 403, 429, and 500.
Status updates
Feezback doesn’t monitor and update statuses of external mandates.
Charging a registered external mandate
Charge a registered external mandate by sending only the customerId. Feezback finds the debtor account and ID details that you registered. You do not send debtorAccount or debtorPsuId.
{
"chargeContext": "chg-00091177",
"customerId": "8834215",
"companyName": "חברה בעמ",
"amount": "1789.47"
}This is a charge line. Send it inside a charge batch, as described in Charging per Mandate. The endpoint, context, executionDate, validation, status codes and webhooks are the same as for any other charge.
As for any mandate that you charge by customerId, the line is checked before it is forwarded to Masav:
| Case | Result |
|---|---|
The customerId is not found | The batch is rejected with 2003, sub-code 20033 |
Feezback does not check that an external mandate is still active at the bank beyond the updates it receives from Masav. If Masav rejects a charge, you receive the usual MandateChargeNotExecuted webhook.
To charge an external mandate you did not register, send debtorAccount and debtorPsuId on the charge line. See Charging per Mandate.
Next steps
- Confirm that your
organizationCodeis whitelisted. - Register a test mandate in the Integration environment.
- Make sure your webhook endpoint handles
MandateStatusChanged. - Submit a charge batch that uses the registered
customerId.
Updated about 6 hours ago