Skip to main content
The JD Connection section defines where the plugin sends its requests. It also sets the ISPB that identifies your institution. Together with JD Credentials, these values make the integration operational. The section header shows a Configured or Not Configured badge. The badge shows Configured when both fields have a value.

​
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. The counterparty bank sees this value as the sender’s institution. By convention, the ISPB is an 8-digit code. The form does not check the length or restrict the value to digits. Make sure you enter the correct value, or the integration does not work.

​
Base URL

The full base URL of the JD SPB environment the plugin connects to (for example https://api.jdspb.com). Always use an HTTPS URL. The plugin sends credentials and transfer data to this endpoint, so an http:// URL exposes them in transit. The form does not check the URL format. Make sure the value is correct before you save. The URL must also match the environment that your JD credentials are valid for. Production credentials against a sandbox URL, or the reverse, cause authentication errors.
A change to the Base URL affects every subsequent transfer. Coordinate the change with your integration team, especially when you move between sandbox and production environments.

​
Saving changes

Click Save in the toolbar at the top of the page. The Settings History tab records every change. After you update 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.