Get started

Follow the steps in Getting started before proceeding. Mambu access: An active account in the Mambu production or sandbox environment. Network connectivity: Verify that your network routes traffic between the Mambu environment and Grand Central iPaaS. For supported options, see Network connectivity. Environment details: You need the following environment details from Mambu to configure the connector:

Parameter	Description
`mambu.baseUrl`	The API endpoint URL for the Mambu environment
`mambu-user-id`	Username for Basic Authentication
`mambu-password`	Password for Basic Authentication

Configuration guide

Follow these steps to initialize and authorize your Mambu Connector.

1. Establish connectivity

Share connectivity details between Grand Central and Mambu as described in Network connectivity.

2. Mambu authentication

The Mambu Connector uses Basic Authentication for API access. To configure authentication, create a Secrets Operations (SOPS) secret. For more information, see How to create SOPS.

To share credentials between Mambu and Grand Central, consider using 1Password.

3. Environment configuration

To initialize the Mambu Connector, define the required environment variables in your gc-applications-live repository. These variables are stored in values.yaml for common configuration across all connectors and in the following files for connector-specific configuration:

Connector	Property	Description
`gc-mambu-deposit-connector`	`deposit-v0.values.yaml`	Outbound deposit connector for deposit account operations
`gc-mambu-deposit-transactions-connector`	`deposit-transactions-v0.values.yaml`	Outbound deposit transactions connector for transaction operations
`gc-mambu-loan-connector`	`loan-v0.values.yaml`	Outbound loan connector for loan account operations
`gc-mambu-loan-transactions-connector`	`loan-transactions-v0.values.yaml`	Outbound loan transactions connector for transaction operations
`gc-mambu-payment-connector`	`payment-v0.values.yaml`	Outbound payment connector for payment operations
`gc-mambu-party-connector`	`party-v0.values.yaml`, `party-v2.values.yaml`	Outbound party connector for party management operations

Define common parameters

These variables are stored in values.yaml and are used across all Mambu connectors:

Parameter	Description	Example value
`existingSecretName`	Reference to SOPS secret containing Mambu credentials.	`mambu`
`mambu.baseUrl`	Target API endpoint for the Mambu environment.	`https://yourbank.sandbox.mambu.com/api`

The following example shows the values.yaml configuration:

# Common Mambu Configuration
# Place this in: values.yaml
connector:
  existingSecretName: mambu
  properties:
    # Mambu Connection Settings
    # mambu.baseUrl: <Mambu_API_Endpoint>
    
    # Forward mapping: product type → Mambu product ID
    # product.<KIND>.<TYPE>.<CURRENCY>.id: <Mambu_Product_ID>
    
    # Reverse mapping: Mambu product ID → product type
    # <Mambu_Product_ID>: product.<KIND>.<TYPE>.<CURRENCY>.id
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO
      json: true

Product ID mapping pattern:

Pattern	Description
`product.{KIND}.{TYPE}.{CURRENCY}.id`	Forward mapping: product type to Mambu product ID
`{MAMBU_PRODUCT_ID}`	Reverse mapping: Mambu product ID to product type

The product ID mappings shown above are examples. Configure the complete mappings based on your Mambu tenant’s product configuration. Contact your Mambu administrator to obtain the full list of product IDs.

Place the values files at the following paths:

iPaaS/azure/runtimes/{runtime}/values/gc-mambu/
├── values.yaml
├── deposit-v0.values.yaml
├── deposit-transactions-v0.values.yaml
├── loan-v0.values.yaml
├── loan-transactions-v0.values.yaml
├── payment-v0.values.yaml
├── party-v0.values.yaml
└── party-v2.values.yaml

Define party connector parameters

The party-v0.values.yaml and party-v2.values.yaml files contain basic configuration for party operations. Product ID mappings are inherited from common values.yaml.

connector:
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO
      json: true

Define deposit connector parameters

The deposit-v0.values.yaml file contains configuration for deposit account operations. Product ID mappings are inherited from common values.yaml.

connector:
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

Define deposit-transactions connector parameters

The deposit-transactions-v0.values.yaml file contains configuration for deposit transaction operations.

connector:
  properties:
    # isMockedDataNeeded: <true|false>
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO
    container:
      limitCPU: 1500m
      limitMemory: 1500Mi
      requestCPU: 1000m
      requestMemory: 1000Mi
    jvm:
      enabled: true
      options:
        - -XX:+UseContainerSupport
        - -XX:+UseParallelGC
        - -XX:MinRAMPercentage=50
        - -XX:MaxRAMPercentage=80

Define loan connector parameters

The loan-v0.values.yaml file contains configuration for loan account operations including product mappings.

connector:
  properties:
    # Forward mapping: product type → Mambu product ID
    # product.<KIND>.<TYPE>.<CURRENCY>.id: <Mambu_Product_ID>
    
    # Reverse mapping: Mambu product ID → product type
    # <Mambu_Product_ID>: product.<KIND>.<TYPE>.<CURRENCY>.id
    
    # timeZone: <TimeZone>
    
    # Error code mappings
    # <CoreErrorCode>: <GC_ErrorCode>
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

Define loan-transactions connector parameters

The loan-transactions-v0.values.yaml file contains configuration for loan transaction operations.

connector:
  properties:
    # isMockedDataNeeded: <true|false>
    # isLoanExistCheck: <true|false>
    # http.client.connection.max.per.route: <Max_Connections>
    # http.client.connection.max.total: <Max_Total_Connections>
    # thread.profile.core.pool.size: <Pool_Size>
    # thread.profile.max.pool.size: <Max_Pool_Size>
    
    # Error code mappings
    # <CoreErrorCode>: <GC_ErrorCode>
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO
    container:
      limitCPU: 1500m
      limitMemory: 1500Mi
      requestCPU: 1000m
      requestMemory: 1000Mi

Define payment connector parameters

The payment-v0.values.yaml file contains configuration for payment operations.

connector:
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

Testing your integration

To access the Payments Unified API, include your Grand Central subscription key in the request header. If you don’t have a key, contact the Grand Central Support Team to request one.

Header	Value
`api-key`	`<your_subscription_key>`

Test the API using the Postman Collection.

Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.

5XX: Internal server error / Core system is down

Cause: The Grand Central gateway cannot establish a handshake with the Mambu endpoint. This typically indicates an upstream service outage at Mambu or a network routing failure.Solution: Verify the operational status of the Mambu environment. Check the Mambu status page or contact Mambu support. If the service is operational, contact Grand Central Support.

5XX: Timeout from core / Read timeout / SocketTimeoutException

Cause: The request to Mambu exceeded the configured timeout period. This may indicate performance issues at Mambu or network latency problems.Solution: Verify the operational status of the Mambu environment and check for any performance degradation. If the service is operational and performing normally, contact Grand Central Support.

401: Invalid authentication credentials

Cause: The user-id or password provided during setup is incorrect, expired, or the user lacks the required permissions in Mambu.Solution: Re-verify your credentials with your Mambu administrator and ensure the user has the required permissions. Contact the Grand Central team to update the connection credentials if needed.

429: Rate limit exceeded

Cause: The number of incoming requests exceeds the defined threshold for your subscription tier. This “429 Too Many Requests” response protects the stability of the Grand Central and Mambu infrastructure.Solution: Review your app’s request patterns to identify unexpected spikes. If you need higher throughput, contact the Grand Central team to request a higher rate limit.

Need more help?

Contact support

Contact the Grand Central team for help with environment setup or rate limit increases.

Overview

Grand Central connectors

Release notes

Configuration guide

1. Establish connectivity

2. Mambu authentication

3. Environment configuration

Define common parameters

Define party connector parameters

Define deposit connector parameters

Define deposit-transactions connector parameters

Define loan connector parameters

Define loan-transactions connector parameters

Define payment connector parameters

Testing your integration

Troubleshooting

Need more help?

Contact support

Overview

Grand Central connectors

Release notes

​Configuration guide

​1. Establish connectivity

​2. Mambu authentication

​3. Environment configuration

​Define common parameters

​Define party connector parameters

​Define deposit connector parameters

​Define deposit-transactions connector parameters

​Define loan connector parameters

​Define loan-transactions connector parameters

​Define payment connector parameters

​Testing your integration

​Troubleshooting

​Need more help?

Contact support

Configuration guide

1. Establish connectivity

2. Mambu authentication

3. Environment configuration

Define common parameters

Define party connector parameters

Define deposit connector parameters

Define deposit-transactions connector parameters

Define loan connector parameters

Define loan-transactions connector parameters

Define payment connector parameters

Testing your integration

Troubleshooting

Need more help?