This integration is powered by Singer's Mambu tap and certified by Stitch. Check out and contribute to the repo on GitHub.
For support, contact Stitch support.
Mambu integration summary
Stitch’s Mambu integration replicates data using the Mambu v2.0 and v1.0 APIs. Refer to the Schema section for a list of objects available for replication.
Mambu feature snapshot
A high-level look at Stitch's Mambu (v2) integration, including release status, useful links, and the features supported in Stitch.
STITCH | |||
Release status | Supported by | ||
Stitch plan |
Standard |
API availability |
Not available |
Singer GitHub repository | |||
REPLICATION SETTINGS | |||
Anchor Scheduling |
Supported |
Advanced Scheduling |
Supported |
Table-level reset |
Unsupported |
Configurable Replication Methods |
Unsupported |
DATA SELECTION | |||
Table selection |
Supported |
Column selection |
Supported |
Select all |
Supported |
||
TRANSPARENCY | |||
Extraction Logs |
Supported |
Loading Reports |
Supported |
Connecting Mambu
Mambu setup requirements
To set up Mambu in Stitch, you need:
-
A Mambu account with API access. The Mambu integration requires an account login with API access. In Mambu’s app, API access can be granted to any existing user.
Step 1: Add Mambu as a Stitch data source
- Sign into your Stitch account.
-
On the Stitch Dashboard page, click the Add Integration button.
-
Click the Mambu icon.
-
Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.
For example, the name “Stitch Mambu” would create a schema called
stitch_mambu
in the destination. Note: Schema names cannot be changed after you save the integration. - In the Subdomain field, enter your Mambu subdomain. For example: If the subdomain were
stitch.mambu.com
, onlystitch
would be entered into this field. - In the Username and Password fields, enter the username and password of the Mambu user with Mambu API access.
Step 2: Define the historical replication start date
The Sync Historical Data setting defines the starting date for your Mambu integration. This means that:
- For tables using Key-based Incremental Replication, data equal to or newer than this date will be replicated to your destination.
- For tables using Full Table Replication, all data - including records that are older, equal to, or newer than this date - will be replicated to your destination.
Change this setting if you want to replicate data beyond Mambu’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.
Step 3: Create a replication schedule
In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
Mambu integrations support the following replication scheduling methods:
-
Advanced Scheduling using Cron (Advanced or Premium plans only)
To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.
Step 4: Set objects to replicate
The last step is to select the tables and columns you want to replicate. Learn about the available tables for this integration.
Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.
For Mambu integrations, you can select:
-
Individual tables and columns
-
All tables and columns
Click the tabs to view instructions for each selection method.
- In the integration’s Tables to Replicate tab, locate a table you want to replicate.
-
To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.
-
To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.
- Repeat this process for all the tables and columns you want to replicate.
- When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
- Click into the integration from the Stitch Dashboard page.
-
Click the Tables to Replicate tab.
- In the list of tables, click the box next to the Table Names column.
-
In the menu that displays, click Track all Tables and Fields:
- Click the Finalize Your Selections button at the bottom of the page to save your data selections.
Initial and historical replication jobs
After you finish setting up Mambu, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.
Free historical data loads
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
Mambu table reference
Schemas and versioning
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is for version 2 of this integration.
Table and column names in your destination
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (CusTomERs
> customers
), while case is maintained in PostgreSQL destinations (CusTomERs
> CusTomERs
). Refer to the Loading Guide for your destination for more info.
activities
Replication Method : |
Key-based Incremental |
Replication Key |
timestamp |
Primary Key |
encoded_key |
API endpoint : |
This table contains information about activities.
encoded_key
The unique encoded activity key. |
|||||||||
timestamp
The time of the activity. |
|||||||||
branch_name
|
|||||||||
client_key
Reference: |
|||||||||
client_name
|
|||||||||
field_changes
|
|||||||||
loan_account_name
|
|||||||||
loan_product_name
|
|||||||||
notes
|
|||||||||
transaction_ID
|
|||||||||
type
|
|||||||||
user_key
Reference:
|
|||||||||
user_name
|
audit_trail
Replication Method : |
Key-based Incremental |
Replication Key |
occurred_at |
Primary Key |
None |
API endpoint : |
This table contains information about activities that have been performed in the Mambu Core Banking system.
event_source
The category of the event: |
request_uri
The part of the request’s URL after the base URL and up to the query string. |
request_method
The HTTP request method. |
request_payload
The raw request data as a string, with sensitive information removed. |
user_agent
The value of HTTP user agent header. |
resource
The resource on which the event occurred. |
resource_fragment
The request URI or raw URL hash. |
username
The user who carried out the action or the name of the API consumer. |
client_ip
The IP address from the HTTP request or the |
response_code
The HTTP response code. |
occurred_at
The date and time the event occurred. |
response_payload
The raw response payload with sensitive information removed. |
branches
Replication Method : |
Key-based Incremental |
Replication Key |
last_modified_date |
Primary Key |
id |
API endpoint : |
This table contains information about branches.
Replication Method : |
Full Table |
Primary Key |
deposit_id : reference_token |
API endpoint : | Parent table : |
This table contains information about cards.
Note: In order to replicate this table, you must also set the deposit_accounts table to replicate.
deposit_id
The deposit ID. |
reference_token
The token used to externally identify the card. |
centres
Replication Method : |
Key-based Incremental |
Replication Key |
last_modified_date |
Primary Key |
id |
API endpoint : |
This table contains information about centres.
id
The unique center ID. |
|||||||||||
last_modified_date
The last date and time that the center was modified. |
|||||||||||
addresses
The list of addresses for a center.
|
|||||||||||
assigned_branch_key
The encoded key of the branch that the center is assigned to. Reference: |
|||||||||||
creation_date
The center creation date. |
|||||||||||
custom_fields
|
|||||||||||
encoded_key
The encoded key of the entity. This value is generated and globally unique. Reference: |
|||||||||||
meeting_day
The day of the week that repayments are collected. |
|||||||||||
name
The center name. |
|||||||||||
notes
Notes about the center. |
|||||||||||
state
The center state. |
clients
Replication Method : |
Key-based Incremental |
Replication Key |
last_modified_date |
Primary Key |
id |
API endpoint : |
This table contains information about clients.
id
The unique client ID. |
|||||||||||
last_modified_date
The last date and time that the client was modified. |
|||||||||||
activation_date
The first date that the client was set as active. |
|||||||||||
addresses
|
|||||||||||
approved_date
The date when the client was approved. |
|||||||||||
assigned_centre_key
Ended key of the center that the client is assigned to. Reference: |
|||||||||||
assigned_user_key
The encoded key of the user that the client is assigned to. Reference:
|
|||||||||||
birth_date
The date that the client born. |
|||||||||||
client_role_key
The role which describes the client’s use within the system. |
|||||||||||
closed_date
The date that the client was closed. |
|||||||||||
creation_date
The date that the client was created. |
|||||||||||
custom_fields
|
|||||||||||
email_address
The client’s email address. |
|||||||||||
encoded_key
The encoded key of the client. This value is generated and globally unique. Reference: |
|||||||||||
first_name
The client’s first name. |
|||||||||||
gender
The client’s gender. |
|||||||||||
group_loan_cycle
The number of paid and closed accounts for this client’s group. |
|||||||||||
home_phone
The client’s home phone number. |
|||||||||||
id_documents
|
|||||||||||
last_name
The client’s last name. |
|||||||||||
middle_name
The client’s middle name. |
|||||||||||
migration_event_key
The encoded key of the migration event that the client is assigned to. |
|||||||||||
mobile_phone
The client’s mobile phone number. |
|||||||||||
notes
Notes about the client. |
|||||||||||
preferred_language
The client’s preferred language selection in Mambu. |
|||||||||||
profile_picture_key
The encoded key of the client’s profile picture. |
|||||||||||
profile_signature_key
The encoded key of the client’s profile signature. |
|||||||||||
state
The state of the client’s workflow status. |
communications
Replication Method : |
Key-based Incremental |
Replication Key |
creation_date |
Primary Key |
encoded_key |
API endpoint : |
This table contains information about communications.
encoded_key
The encoded key of the communication. This value is generated and unique. |
|||
creation_date
The date and time the communication was created - as UTC. |
|||
body
The message body text. |
|||
client_key
The client the message was sent to. Reference: |
|||
custom_fields
|
|||
deposit_account_key
The deposit account about which the message was sent. Reference: |
|||
destination
The phone number or email address that the communication was sent to. |
|||
event
The event for which the message was sent. |
|||
failure_cause
The failure code of the failed message. |
|||
failure_reason
The reason the message failed to send. |
|||
group_key
The group that the message was sent to. Reference: |
|||
loan_account_key
The load account for which the message was sent. Reference: |
|||
num_retries
The number of retries to send the message. |
|||
reference_id
The reference ID of the communication. This value is generated by the SMS Dispatcher. |
|||
repayment_key
The repayment about which the the message was sent. |
|||
send_date
The date and time the communication was actually sent - as UTC. |
|||
sender_key
The encoded key of the sender. Reference:
|
|||
state
The state of the message. |
|||
subject
The subject of the message. |
|||
template_key
The communication template key. |
|||
type
The type of communication. |
|||
user_key
The user the message was sent to. Reference:
|
credit_arrangements
Replication Method : |
Key-based Incremental |
Replication Key |
last_modified_date |
Primary Key |
id |
API endpoint : |
This table contains information about credit arrangements.
id
The unique credit arrangement ID. |
|||
last_modified_date
The last date and time that the credit arrangement was modified. |
|||
amount
The maximum credit amount the client can be exposed to. |
|||
approved_date
The date the credit arrangement was approved. |
|||
available_credit_amount
The amount of credit available in the arrangement. |
|||
consumed_credit_amount
The amount of credit used. This is the difference taken from the amount and available credit amount. |
|||
creation_date
The date the credit arrangement was created. |
|||
custom_fields
|
|||
encoded_key
The encoded key of the credit arrangement. This value is auto-generated and unique. Reference: |
|||
expire_date
The date the credit arrangement expires. |
|||
holder_key
The encoded key of the client or group. Depending on the |
|||
holder_type
The line of credit holder’s type - client or group. |
|||
notes
The description of the credit arrangement. |
|||
start_date
The start date from which the credit arrangement becomes active. |
|||
state
The state of the credit arrangement. Possible values are:
|
|||
sub_state
The substate of the credit arrangement. This will either be |
custom_field_sets
Replication Method : |
Full Table |
Primary Key |
id |
API endpoint : |
This table contains information about custom field sets.
id
The custom field set ID. Reference:
|
|||||||||||||||||||||||||||||||||
created_date
|
|||||||||||||||||||||||||||||||||
custom_fields
|
|||||||||||||||||||||||||||||||||
encoded_key
|
|||||||||||||||||||||||||||||||||
index_in_list
|
|||||||||||||||||||||||||||||||||
last_modified_date
|
|||||||||||||||||||||||||||||||||
name
|
|||||||||||||||||||||||||||||||||
notes
|
|||||||||||||||||||||||||||||||||
type
|
|||||||||||||||||||||||||||||||||
usage
|
deposit_accounts
Replication Method : |
Key-based Incremental |
Replication Key |
last_modified_date |
Primary Key |
id |
API endpoint : |
This table contains information about deposit accounts.
Note: This table must be selected to replicate the following tables:
id
The deposit account ID. |
||||||||||||
last_modified_date
The date and time the deposit account was last modified. |
||||||||||||
account_holder_key
The encoded key of the client or group that holds the account. Depending on the |
||||||||||||
account_holder_type
The type of the account holder. |
||||||||||||
account_state
The state of the deposit account. |
||||||||||||
account_type
The type of deposit account. |
||||||||||||
accrued_amounts
Groups all fields related to a deposit account’s accrued amounts.
|
||||||||||||
activation_date
The date this deposit account was activated. |
||||||||||||
approved_date
The date this deposit account was approved. |
||||||||||||
balances
Groups all fields related to a deposit account’s balances.
|
||||||||||||
closed_date
The date this deposit account was closed. |
||||||||||||
creation_date
The date this deposit account was created. |
||||||||||||
credit_arrangement_key
The key to the credit arrangement where this account is registered to. Reference: |
||||||||||||
currency_code
|
||||||||||||
custom_fields
|
||||||||||||
encoded_key
Reference: |
||||||||||||
interest_settings
|
||||||||||||
internal_controls
|
||||||||||||
last_account_appraisal_date
|
||||||||||||
last_interest_calculation_date
|
||||||||||||
last_interest_stored_date
|
||||||||||||
last_overdraft_interest_review_date
|
||||||||||||
last_sent_to_arrears_date
|
||||||||||||
linked_settlement_account_keys
|
||||||||||||
locked_date
|
||||||||||||
maturity_date
|
||||||||||||
migration_event_key
|
||||||||||||
name
|
||||||||||||
notes
|
||||||||||||
overdraft_interest_settings
|
||||||||||||
overdraft_settings
|
||||||||||||
product_type_key
|
||||||||||||
withholding_tax_source_key
|
deposit_products
Replication Method : |
Key-based Incremental |
Replication Key |
last_modified_date |
Primary Key |
id |
API endpoint : |
This table contains information about deposit (savings) products.
id
The deposit product ID. |
|||||||||||||||||||||||||||||||||||||||||||
last_modified_date
The date and time the deposit product was last modified. |
|||||||||||||||||||||||||||||||||||||||||||
accounting_method
|
|||||||||||||||||||||||||||||||||||||||||||
activated
|
|||||||||||||||||||||||||||||||||||||||||||
allow_arbitrary_fees
|
|||||||||||||||||||||||||||||||||||||||||||
allow_offset
|
|||||||||||||||||||||||||||||||||||||||||||
allow_overdraft
|
|||||||||||||||||||||||||||||||||||||||||||
allow_technical_overdraft
|
|||||||||||||||||||||||||||||||||||||||||||
available_product_branches
|
|||||||||||||||||||||||||||||||||||||||||||
collect_interest_when_locked
|
|||||||||||||||||||||||||||||||||||||||||||
creation_date
|
|||||||||||||||||||||||||||||||||||||||||||
currencies
|
|||||||||||||||||||||||||||||||||||||||||||
custom_field_values
|
|||||||||||||||||||||||||||||||||||||||||||
description
|
|||||||||||||||||||||||||||||||||||||||||||
encoded_key
|
|||||||||||||||||||||||||||||||||||||||||||
for_all_branches
|
|||||||||||||||||||||||||||||||||||||||||||
for_groups
|
|||||||||||||||||||||||||||||||||||||||||||
for_individuals
|
|||||||||||||||||||||||||||||||||||||||||||
id_generator_type
|
|||||||||||||||||||||||||||||||||||||||||||
id_pattern
|
|||||||||||||||||||||||||||||||||||||||||||
interest_accrued_accounting_method
|
|||||||||||||||||||||||||||||||||||||||||||
interest_calculation_balance
|
|||||||||||||||||||||||||||||||||||||||||||
interest_days_in_year
|
|||||||||||||||||||||||||||||||||||||||||||
interest_paid_into_account
|
|||||||||||||||||||||||||||||||||||||||||||
interest_payment_point
|
|||||||||||||||||||||||||||||||||||||||||||
interest_rate_settings
|
|||||||||||||||||||||||||||||||||||||||||||
line_of_credit_requirement
|
|||||||||||||||||||||||||||||||||||||||||||
maturity_period_limit
|
|||||||||||||||||||||||||||||||||||||||||||
max_overdraft_limit
|
|||||||||||||||||||||||||||||||||||||||||||
min_opening_balance
|
|||||||||||||||||||||||||||||||||||||||||||
name
|
|||||||||||||||||||||||||||||||||||||||||||
overdraft_days_in_year
|
|||||||||||||||||||||||||||||||||||||||||||
overdraft_interest_rate_settings
|
|||||||||||||||||||||||||||||||||||||||||||
product_type
|
|||||||||||||||||||||||||||||||||||||||||||
savings_fees
|
|||||||||||||||||||||||||||||||||||||||||||
savings_product_rules
|
|||||||||||||||||||||||||||||||||||||||||||
templates
|
|||||||||||||||||||||||||||||||||||||||||||
withholding_tax_enabled
|
deposit_transactions
Replication Method : |
Key-based Incremental |
Replication Key |
creation_date |
Primary Key |
encoded_key |
API endpoint : |
This table contains information about deposit transactions.
encoded_key
The unique encoded key of the deposit transaction. |
|||||||||||||||
creation_date
The date when the deposit transaction was created. |
|||||||||||||||
account_balances
|
|||||||||||||||
adjustment_transaction_key
|
|||||||||||||||
affected_amounts
|
|||||||||||||||
amount
|
|||||||||||||||
booking_date
|
|||||||||||||||
branch_key
Reference: |
|||||||||||||||
card_transaction
|
|||||||||||||||
centre_key
Reference: |
|||||||||||||||
currency_code
|
|||||||||||||||
custom_fields
|
|||||||||||||||
external_id
|
|||||||||||||||
fees
|
|||||||||||||||
id
|
|||||||||||||||
linked_loan_transaction_key
Reference: |
|||||||||||||||
migration_event_key
|
|||||||||||||||
notes
|
|||||||||||||||
original_transaction_key
|
|||||||||||||||
parent_account_key
|
|||||||||||||||
taxes
|
|||||||||||||||
terms
|
|||||||||||||||
till_key
|
|||||||||||||||
transaction_details
|
|||||||||||||||
transfer_details
|
|||||||||||||||
type
|
|||||||||||||||
user_key
Reference:
|
|||||||||||||||
value_date
|
gl_accounts
Replication Method : |
Key-based Incremental |
Replication Key |
last_modified_date |
Primary Key |
gl_code |
API endpoint : |
This table contains information about general ledger accounts.
gl_code
The unique general ledger code. Reference: |
|||||||
last_modified_date
The time the GL account was last modified. |
|||||||
activated
|
|||||||
allow_manual_journal_entries
|
|||||||
balance
|
|||||||
creation_date
|
|||||||
currency
|
|||||||
encoded_key
|
|||||||
entry_id
|
|||||||
name
|
|||||||
strip_trailing_zeros
|
|||||||
type
|
|||||||
usage
|
gl_journal_entries
Replication Method : |
Key-based Incremental |
Replication Key |
booking_date |
Primary Key |
entry_id |
API endpoint : |
This table contains information about general ledger entries.
entry_id
The GL journal entry ID. |
booking_date
The journal entry booking date. |