Skip to main content
The JD Credentials section holds the authentication details the Bank Transfer plugin uses to authenticate against the JD SPB integration. Without these values, the plugin cannot send or receive transfers. The section header shows a Configured or Not Configured badge based on whether both a Legacy Code and a User Code are present.

​
Accessing the section

1

Open Settings

In the Bank Transfer sidebar, click Settings.
2

Expand JD Credentials

The section is the first one on the page and is expanded by default.

​
Fields

​
Legacy Code

The legacy client identifier issued by JD. The form does not enforce this field, but the JD integration typically needs it populated to authenticate correctly.

​
User Code

The user identifier associated with the credentials. The form does not enforce this field, but the JD integration typically needs it populated to authenticate correctly.

​
Password

The password associated with the user. Stored as a secret and never displayed after saving — the field shows placeholder dots instead of the stored value. Leave it empty when saving to keep the previously stored password unchanged.

​
Private Key (PEM)

The PEM-encoded private key used to sign requests to JD. It must be an RSA private key in PEM format — JD SPB signatures use RSA PKCS#1 v1.5 with SHA-256, and a key size of at least 2048 bits is required. Also treated as a secret: the stored value is never displayed back and the field shows placeholder dots. Leave it empty to keep the existing value.

​
Signature Required

Toggle that enables or disables request signing using the private key. Turn it on when JD expects signed requests, off otherwise.
JD Credentials are highly sensitive. Treat the Legacy Code, User Code, Password, and Private Key as production secrets: restrict edit access, avoid sharing screenshots with these fields visible, and rotate them through your organization’s standard secret-rotation process.

​
Saving changes

After editing the fields, click Save in the toolbar at the top of the page. The plugin submits only the fields you changed; secret fields left empty keep their current stored value. Every change is recorded in the Settings History tab. Secret values are stored but displayed as masked placeholders (••••) in the history, so you can see when a secret changed without exposing its content.