BDI
תוכן זה אינו זמין עדיין בשפה שלך.
This feature needs to be activated. Please inquire details with our support.
BDI integration refers to “Coface bdi”. This integration include out-the-box data exchange with coface based on data inserted into a form. The flow is:
- User insert a data, i.e. loan amount, id etc..
- Data is posted securely to coface
- Result is returned to form so further implementation can be carried out such as hide or show parts of the form based on success or failure
What needs to be done prior to the following steps?
Section titled “What needs to be done prior to the following steps?”- Make sure you have an API account with BDI for personal check. make sure the following data handy: Username, password, Terminal ID, Credit provider code
- Make sure you have received clearance to use BDI from our support team
How to set up BDI
Section titled “How to set up BDI”Once BDI is available for your disposal please carry out the following configuration
Setup web-hook
Section titled “Setup web-hook”- Login to cellosign app and click to add new web hook from web hook pane
- Provide a name for your integration
- Select type: “Get data from remote source” (Field change API)
- Turn off switch “Use implicit”
- Insert URL provided.
- Add the following header and corresponding values
- “X-BDI-TermID”: Value is the terminal ID provided from BDI
- “X-BDI-CreditProviderCode”: Value is your credit provider code you received from BDI
- In authentication section, Select “Basic” and enter the username and password you received from BDI
Note: Parameters are encrypted and are not displayed in cellosign interface
Template configuration
Section titled “Template configuration”Select the template that requires integration with BDI and follow these steps
- Open integrations tab
- Click “Add live connector”
- Select Webhook for source
- Select the webhook you created in previous stage (by name)
- Select the trigger: Field change or click. We advise to use click.
- Add the following fields to the mapper. make sure that the configuration includes the field name or alias exactly as in alias column (Note capital and small letters)
| Alias | What it does | Notes and data validation |
|---|---|---|
| FirstName | Client first name | Outgoing, Mandatory Make sure to set “Hebrew characters” only in field configuration |
| LastName | Client last name | Outgoing, Mandatory Make sure to set “Hebrew characters” only in field configuration |
| ID | Client ID number | Outgoing, Mandatory Make sure to select Cellosign ID field |
| result | This is the options for returning values - “1” success (related to cwa_code) - “2” error. This represents a legitimate error. Details can be retrieved from the following parameters - “9999” Unexpected error. Interface not available or any technical error, Typically this is not related to client data. | Incoming Mandatory. |
| bdi_error_code | Retrieve value from “ErrCode” in “BDI_Error” object | Incoming, Optional |
| bdi_error_desc | Retrieve value from “ErrDescription” in “BDI_Error” object | Incoming, Optional |
| ccr_error_code | Retrieve value from “Code” in “CCR_Error” object | Incoming, Optional |
| ccr_error_desc | Retrieve value from “Description” in “CCR_Error” object | Incoming, Optional |
| ccr_error_sev | Retrieve value from “Severity” in “CCR_Error” object | Incoming, Optional |
Limitations
Section titled “Limitations”- interface support Israeli ID, Passport is not supported
- Interface is limited to personal check. Company