canonical: https://jentic.com/apis/swaggerhub.asig/debit-authorizations

# Asig Debit Authorizations

A buyer business wants to provide its bank account number or virtual card number, details on purpose of payment, and authorization for the supplier to debit the provided account number. The buyer wishes to receive a real time acknowledgement when the instructions have been received. The API exposes 1 endpoints secured with apiKey authentication.

## For AI agents

Programmatically authorize to pay - request. Covers 1 operations with apiKey authentication.

## Scope

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

## Capabilities

- Authorize to Pay - Request
- Manage payments data programmatically
- Integrate Debit Authorizations into automated workflows
- Query and filter Debit Authorizations records by parameters
- Monitor Debit Authorizations operational status and events

## Use cases

### Payments Operations

Use the Debit Authorizations to perform payments operations programmatically. The API provides 1 endpoints covering core functionality including authorize to pay - request.

Example prompt: Call POST /debitauthorizations to authorize to pay - request

### Data Retrieval and Monitoring

Query Debit Authorizations resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary Debit Authorizations endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Debit Authorizations 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 apiKey tokens manually.

Example prompt: Search Jentic for 'authorize to pay - request', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /debitauthorizations | Authorize to Pay - Request |

## Key resources

- **Debitauthorizations** — Operations for debitauthorizations

## Why Jentic

- **Setup:** Wiring the Debit Authorizations API by hand means placing its apikey in the query string on every call against the api.afinis.org host and formatting the debit authorization POST yourself. Through Jentic you install once, import the Debit Authorizations API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The authorization details for this API travel in the request body, not the URL path, so scope by operation: limit the agent to the operations it needs, such as requesting a debit authorization, and leave everything else out. You choose the operations it may call, so it does only what you allow.
- **Credential handling:** Your Debit Authorizations API key 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 'request a debit authorization to pay', and Jentic returns the matching 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 Debit Authorizations use?

The Debit Authorizations uses an API key passed in the `apikey` query. 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 authorize to pay - request with the Debit Authorizations?

Yes. Use the POST /debitauthorizations endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Debit Authorizations?

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 authorize to pay - request through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'authorize to pay - request'. Jentic returns the matching Debit Authorizations operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Debit Authorizations have?

The Debit Authorizations exposes 1 endpoints covering debitauthorizations operations.

### Can I limit what my agent is allowed to do with the Debit Authorizations API?

Yes. Because you run Jentic One yourself, your own rules decide which Debit Authorizations operations and credentials the agent may use. This API exposes a single operation, POST /debitauthorizations for requesting a debit authorization, so you scope by operation: allow only that call and leave everything else out. The agent does exactly what you permit and nothing more.