canonical: https://jentic.com/apis/tenant_name.mambu.com/tenant-name-mambu

# Tenant Name Mambu Payment Order API

Initiates payment orders. The API exposes 46 endpoints.

## For AI agents

Programmatically sepadirectdebit_addblockingrule, sepadirectdebit_removeblockingrules. Covers 46 operations.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- SepaDirectDebit_addBlockingRule
- SepaDirectDebit_removeBlockingRules
- ExternalAccountRepresentation_addIdentificationAssociation
- ExternalAccountRepresentation_getIdentifications
- ExternalAccountRepresentation_associateIban
- ExternalAccountRepresentation_searchIdentifications
- SepaDirectDebit_createCollectionInitiationRequest

## Use cases

### Payments Operations

Use the Payment Order API to perform payments operations programmatically. The API provides 46 endpoints covering core functionality including sepadirectdebit_addblockingrule, sepadirectdebit_removeblockingrules, externalaccountrepresentation_addidentificationassociation.

Example prompt: Call POST `/accounts/{accountId}/blocking-rules` to sepadirectdebit_addblockingrule

### Automated SEPA Credit Transfers Management

Automate sepa credit transfers operations by combining multiple Payment Order API endpoints. Agents can sepadirectdebit_removeblockingrules and then externalaccountrepresentation_addidentificationassociation in a single workflow.

Example prompt: Call DELETE `/accounts/{accountId}/blocking-rules` to sepadirectdebit_removeblockingrules, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Payment Order API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'sepadirectdebit_addblockingrule', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/accounts/{accountId}/blocking-rules` | SepaDirectDebit_addBlockingRule |
| DELETE | `/accounts/{accountId}/blocking-rules` | SepaDirectDebit_removeBlockingRules |
| POST | `/accounts/{accountId}/identifications` | ExternalAccountRepresentation_addIdentificationAssociation |
| GET | `/accounts/{accountId}/identifications` | ExternalAccountRepresentation_getIdentifications |
| PUT | `/accounts/identifications` | ExternalAccountRepresentation_associateIban |
| POST | `/accounts/identifications:search` | ExternalAccountRepresentation_searchIdentifications |
| POST | `/collections` | SepaDirectDebit_createCollectionInitiationRequest |
| POST | `/log` | ExternalAccountRepresentation_createOrUpdateLog |

## Key resources

- **SEPA Credit Transfers** — These endpoints are used for making and receiving SEPA credit transfers through the Mambu Payment Ga
- **SEPA Direct Debit** — SEPA Direct Debit Payments are one time or recurring payments made using the Single European Payment
- **SEPA Credit Transfer Inquiries** — These APIs allow you to submit inquiries for SEPA payments including for cases where the customer cl
- **External Account Representation** — The External Account Representation (EAR) endpoints are used to associate IBANs with Mambu account I
- **Standing Order** — Operations related to Standing Order

## Why Jentic

- **Setup:** Wiring the Mambu Payment Order API by hand means pointing at your own tenant host (TENANT_NAME.mambu.com/api/v1) and handling account, identification, and collection calls yourself. Through Jentic you install once, import the Payment Order API from the API Directory, store your tenant credential once, and your agent calls it.
- **Permission scoping:** The Payment Order API puts the account id in the URL path (`/accounts/{accountId}/blocking-rules`), so a rule can pin your agent to one account: it can add identifications and read blocking rules for that account and nothing else. You choose the operations it may call, so deleting blocking rules is not included unless you add it.
- **Credential handling:** Your Mambu tenant credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'add a blocking rule to an account' or 'search account identifications', and Jentic returns the matching Payment Order API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Payment Order API use?

The Payment Order API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I sepadirectdebit_addblockingrule with the Payment Order API?

Yes. Use the POST `/accounts/{accountId}/blocking-rules` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Payment Order API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I sepadirectdebit_addblockingrule through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'sepadirectdebit_addblockingrule'. Jentic returns the matching Payment Order API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Payment Order API have?

The Payment Order API exposes 46 endpoints covering sepa credit transfers, sepa direct debit, sepa credit transfer inquiries operations.

### Can I limit what my agent is allowed to do with the Payment Order API?

Yes. Jentic One runs self-hosted, so your own rules decide which Payment Order API operations and credentials the agent may use. Because the account id sits in the URL path, such as `/accounts/{accountId}/blocking-rules`, you can pin the agent to a single account and allow only the calls you approve, for example adding identifications and reading that account's blocking rules. Destructive calls like DELETE `/accounts/{accountId}/blocking-rules` stay off unless you explicitly add them.