Skip to main content
The Mambu integration includes several outbound (synchronous) runtime connectors that call the Mambu API v2. Backbase configures each connector in its own values.yaml file. For the environment details you send to Backbase, see Get started.

Configuration properties

Values to obtain from Mambu

Obtain the following value from Mambu and send it to your Backbase support team. Backbase sets it in values.yaml. This value is environment-specific, so it has no default.

Common properties

Set these properties in values.yaml. They apply across all Mambu connectors. Product ID mappings set here are inherited by the deposit and party connectors. The following product ID mapping patterns translate between Banking OS product types and Mambu product IDs.
The product ID mapping values are environment-specific. Contact your Mambu administrator to obtain the full list of product IDs for your tenant.

gc-mambu-party-connector and gc-mambu-deposit-connector

The party and deposit connectors hold basic configuration. They inherit the product ID mappings from the common values.yaml. They have no additional connector-specific properties.

gc-mambu-deposit-transaction-connector

Set this property in deposit-transactions-v0.values.yaml, in addition to the common properties.

gc-mambu-loan-connector

Set these properties in loan-v0.values.yaml, in addition to the common properties.

gc-mambu-loan-transaction-connector

Set these properties in loan-transactions-v0.values.yaml, in addition to the common properties.

gc-mambu-payment-connector

Set this property in payment-v0.values.yaml. The payment connector uses the common properties and defines the following connector-specific error-code overrides.

SOPS secrets

The connectors use Basic authentication with credentials stored in a SOPS secret, referenced by the existingSecretName property. Obtain the following credentials from Mambu. Backbase stores the secret.

Supported operations

The Mambu connectors expose the Banking OS Unified API. For the operation-to-endpoint tables per domain (deposit, deposit transactions, loan, loan transactions, payment, party), see Overview. For the full contract, see the API playground.

Events

These connectors are synchronous and do not publish or consume events.

Error mapping

The connector maps Mambu error codes to Banking OS status codes. For the full list, see Error codes. You can configure connector-specific overrides as core-to-Banking OS code pairs in a connector’s values.yaml; the payment connector ships with overrides for several Mambu error codes (see gc-mambu-payment-connector). The loan and loan transaction connectors also accept overrides through the <CoreErrorCode> property.

Dependencies

  • Mambu API v2 (outbound), reachable at mambu.baseUrl.
  • The shared mambu-connector-sdk library.