Configuration Guide
JWT payload configuration guide
Example payload:
{
"iss": "tpp/987654",
"srv": "mandate/user",
"sub": "user-00112233",
"flow": {
"userWasAuthenticated": true,
"context": "tx-20250113001",
"userIdentifier": {
"type": "ID",
"value": "200200202",
"editable": true
},
"mandate": {
"creditor": {
"name": "Electric Company Ltd",
"organizationCode": "24562"
},
"debtor": {
"account": "IL710110950000102188000",
"accountType": "iban",
"editable": true
},
"redirects": {
"success": "https://merchant.com/success",
"failure": "https://merchant.com/failure",
"notComplete": "https://merchant.com/notComplete",
"ttlExpired": "https://merchant.com/session-expired"
}
}
}
}JWT fields
| Field | Type | Required | Description |
|---|---|---|---|
iss | string | Yes | Issuer value in the format tpp/{TPP_ID}. |
srv | string | Yes | Service selector. Use mandate/user for mandate authorization flows. |
sub | string | Yes | User identifier for the mandate flow. |
flow | object | Yes | Mandate flow configuration. |
Flow fields
Configure userIdentifier
userIdentifier- The userIdentifier object allows you to set the debtor's identification.
- Use it in cases you have the debtor's government ID (for example, after in-app/website authentication).
- Consider wether you want it editable or locked. Enable editing when you can receive payments from a different ID. Disable editing when you want The transfer from a specific ID holder.
- All fields within the object are mandatory if the object is sent
- Defining userIdentifier is optional. If not sent with the JWT, the debtor will be prompted to fill out their ID (you will receive it with the webhook at the end of the process)
Configure corporateIdentifier
corporateIdentifier- The corporateIdentifier object allows you to set the debtor's corporate identification (in case your debtor is a corporate and you have their business number (ח.פ.)
- If you don't have it, no worries: the debtor will add it on Feezback screens.
Configure mandate fields
mandate fieldsConfigure a public link
What is a public link?
A Feezback link that can be used universally to get payments from anyone, without predefined payment and debtor details.
- No prefilled data: all fields will be entered by the debtor.
- Reusable: enables multiple usage by different debtors.
- Non expiring: the link will not have an expiration time and will be available indefinitely.
- Easy display: short link or QR code.
When to use it?
Generate a public link when you you don't need to assign the link to a specific flow on your side.
Public links has predefined settings that are not configured per payment. It is a one size fits all solution.
How to generate a public link?
- Generate a Feezback Mandate Link without userIdentifier and without debtor account.
- Add the "publicLink" object to the payment link request "flow" object.
- Add custom fields if you want to collect additional details from the debtor (you will get these values back in the status update webhooks.
{
"publicLink": {
"customFields": [
{"name": "agentIdentifier"},
{"name": "phoneNumber"},
{"name": "debtorName"}
]
},Updated about 1 month ago
Did this page help you?