Skip to main content
The JD Connection section defines where the plugin sends its requests and which ISPB it identifies itself with. Together with JD Credentials, these values make the integration operational. The section header shows a Configured or Not Configured badge based on whether both fields are filled in.

​
Accessing the section

1

Open Settings

In the Bank Transfer sidebar, click Settings.
2

Expand JD Connection

Click the section header to expand it.

​
Fields

​
Origin ISPB

The ISPB that identifies your institution as the origin of outbound TED transfers. This value appears to the counterparty bank as the sender’s institution. By convention, the ISPB is an 8-digit code, but the form does not enforce length or digit-only formatting — make sure you enter the correct value for the integration to work.

​
Base URL

The full base URL of the JD SPB environment the plugin should talk to (for example https://api.jdspb.com). Always use an HTTPS URL: credentials and transfer data are sent to this endpoint, so an http:// URL would expose them in transit. The form does not validate URL formatting, so double-check the value before saving. Make sure it matches the environment your JD credentials are valid for — using production credentials against a sandbox URL, or vice versa, will cause authentication errors.
Changing the Base URL affects every subsequent transfer. Coordinate the change with your integration team, especially when moving between sandbox and production environments.

​
Saving changes

Click Save in the toolbar at the top of the page. Every change is recorded in the Settings History tab. After updating the connection, check the plugin’s Dashboard for the health indicator. If the integration cannot reach the new endpoint, the status changes to Down and the degradation banner appears.