Supported Grand Central unified API specification operations
The Mambu connector supports the following operations from the Grand Central Unified API Specification:| Grand Central Unified API Specification domain | Operation | Description |
|---|---|---|
| Deposit Account | Create a new deposit account | Initiates the creation of new customer deposit accounts, including customer account validation, and the generation of account details. |
| Get deposit account balances | Fetch the balances of one or more deposit accounts by specifying their unique identifiers (account IDs). | |
| Get deposit account details | Fetch the details of one or more deposit accounts by specifying their unique identifiers (account IDs). | |
| Update deposit account details | Update and make changes or modifications to the information associated with a particular deposit account. This could include various aspects, such as customer details, account settings, or other relevant information. | |
| Close an inactive deposit account | Identify inactive deposit accounts based on predefined criteria, such as no withdrawals, deposits, or transactions within a specified time frame. Once an inactive account is identified, the connector initiates the closure process. |
Deposit account numbers must be generated by your financial institution. Account numbers and account IDs are mapped through custom fields only. For the Grand Central connectors, Mambu only returns account IDs.
| Grand Central Unified API Specification domain | Operation | Description |
|---|---|---|
| Deposit Account Transaction | Get transaction details of multiple accounts | Access and retrieve transaction information for several deposit accounts simultaneously. |
| Retrieve account transactions based on filters | Retrieve specific deposit account transactions using predefined filters such as date ranges, transaction types, account IDs, etc. | |
| Get account transaction details by transaction ID | Fetch the transaction details by specifying their unique identifiers (transaction IDs). | |
| Loan Account | Create a loan account | Initiates the creation of a loan account, including setting up a record for a customer to manage a loan, with details such as the loan amount, interest rate, repayment terms, and other relevant information. |
| Get loan accounts details | Retrieve details related to loan accounts, such as loan balances, payment schedules, interest rates, and other relevant data associated with individual loan accounts. | |
| Get loan account by loan ID | Fetch the details of one or more accounts by specifying their unique identifiers (loan IDs). | |
| Get loan amortization schedule details | Retrieve specific details related to the amortization schedule of a loan. In financial terms, an amortization schedule outlines the repayment of a loan over time, specifying each installment’s breakdown into principal and interest. | |
| Get loan amortization payment details | Retrieve specific details related to loan amortization payments, including information about each scheduled payment, such as the principal amount, interest, total payment, remaining balance, and the payment date. | |
| Loan Account Transaction | Get transaction details for multiple loans | Retrieve details related to loan accounts, such as loan balances, payment schedules, interest rates, and other relevant data associated with individual loan accounts. |
| Retrieve loan transactions based on filters | Retrieve specific loan transactions based on specified filters, including criteria such as date ranges, loan types, customer identifiers, or other relevant parameters. | |
| Retrieve details of loan transaction by transaction ID | Fetch information about a particular loan transaction based on its unique identifier, the transaction ID. | |
| Payment | Initiate a payment | Initiates payment transactions, including functionalities such as fund transfers, bill payments, or any other financial transactions supported by the connector. |
| Party | Create party | Create a new party record. A party refers to an individual, organization, or entity that is a participant in a business process. Parties can represent customers, clients, suppliers, or any other entities relevant to the system. |
| Update parties details | Update or modify information related to parties, including customers, clients, or entities within the system. | |
| Get party details | Fetch the details of one or more party records by specifying their unique identifiers (party IDs). | |
| Update party by party ID | Update party records by specifying their unique identifiers (party IDs). | |
| Patch party by party ID | Patch party records by specifying their unique identifiers (party IDs). | |
| Search party | Search for a party record using one of the following criteria: • party ID • party name: search by specifying the initial characters of the name • deposit account ID | |
| Retrieve account balances that belong to the party details specified | Fetch account balance information related to a specified party, providing insights into the financial status associated with that particular entity. | |
| Retrieve accounts that belong to the party details specified | Retrieve information about accounts associated with a specific party (customer or entity). |
Error mapping
Mambu to Grand Central
| Mambu code | GC code | Implemented connector |
|---|---|---|
301 | GC101 | Common |
4 | GC055 | Common |
428 | GC201 | Common |
2102 | GC055 | Common |
100 | GC501 | Common |
116 | GC205 | Common |
513 | GC204 | Common |
212 | GC303 | Common |
212 | GC301 | gc-mambu-transaction-connector |
4 | GC055 | gc-mambu-payment-connector• If payee account is invalid, Mambu sends a generic request validation failure error. |
428 | GC401 | gc-mambu-payment-connector• If payer account is invalid. |
For a complete list of Grand Central error codes and their descriptions, see error codes reference.