Tenant Name Mambu Payment Order API

Name: Payment Order API
Brand: Payment Order API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingnone46 EndpointsREST

For Agents

Programmatically sepadirectdebit_addblockingrule, sepadirectdebit_removeblockingrules. Covers 46 operations.

Install Jentic One Beta

Connect the Payment Order API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Payment Order API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftenant_name.mambu.com%2Ftenant-name-mambu" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftenant_name.mambu.com%2Ftenant-name-mambu" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Payment Order API.

SepaDirectDebit_addBlockingRule

SepaDirectDebit_removeBlockingRules

ExternalAccountRepresentation_addIdentificationAssociation

ExternalAccountRepresentation_getIdentifications

GET STARTED

Start building with Payment Order API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Payment Order API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

46 endpoints — initiates payment orders.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Payment Order API through Jentic.

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.

Tenant Name Mambu Payment Order API

Connect the Payment Order API to your agent

Capabilities

Start building with Payment Order API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs