Skip to main content
Follow the steps in Get started with connectors before proceeding. SaltEdge access: An active SaltEdge Data Enrichment contract and the credentials required for API and webhook authentication. Network connectivity: Network connectivity between Banking OS and SaltEdge. For supported options, see Network connectivity.

Prepare the connector

Backbase deploys this connector. To share connectivity details and provide the environment details, follow these steps:
  1. Share connectivity details. Share connectivity details between Banking OS and SaltEdge as described in Network connectivity.
  2. Send environment details to Backbase. Send the SaltEdge base URL, customer ID, App-Id, and App-Secret to your Backbase support team. Banking OS sends the application ID and secret to SaltEdge as request headers.
  3. Register the webhook with SaltEdge. Ask your Backbase support team for the categorization webhook URL, then register that URL with SaltEdge.
For property names and defaults, see Reference.

Test your integration

  1. Call POST {baseURL}/internal/transactions/enrichment with a test batch. The batch must include a unique enrichmentRequestId, a partyInformation array, and at least one entry in accounts.
  2. Confirm Banking OS returns 202 with an empty body.
  3. When SaltEdge sends the categorization callback to POST {baseInboundURL}/webhooks/transaction-categorizations, confirm the connector publishes transactionsEnriched to Sync Hub.
  4. Verify downstream consumers receive the expected enrichment payload.
For operation and event details, see Reference. For the full contract, see API playground.

Troubleshooting

If the connector does not respond as expected, check these common scenarios.
Cause: SaltEdge application credentials or webhook signing details are missing or incorrect.Solution: Verify credentials with SaltEdge, then ask your Backbase support team to update the connection.
Cause: Banking OS cannot reach the SaltEdge Data Enrichment endpoint within the configured timeout.Solution: Confirm network routing and the operational status of the SaltEdge environment.
Cause: The SaltEdge webhook callback did not reach Banking OS, or ASB producer properties point to the wrong topic.Solution: Confirm the callback URL registered with SaltEdge is the URL from your Backbase support team. Ask that team to check Sync Hub publishing if the callback arrives and no event is published.