canonical: https://jentic.com/apis/destaxa.com/destaxa

# Destaxa DTX Pro - API

The Destaxa DTX Pro API reports on card payment reconciliation: it returns sales records and the receivables a merchant is owed by their acquirers. You pull sales details and summaries, chart how sales evolve over time, and read a receivables calendar with summaries, daily totals, per-sale breakdowns, and consolidated views. Filter endpoints list the transaction categories, card brands, and acquirers available to scope a query, so a finance tool can slice reconciliation data the way it needs.

## For AI agents

Report on card payment reconciliation with Destaxa DTX Pro: pull sales details and summaries, chart sales evolution, and read a receivables calendar with daily totals and breakdowns. Lists filter options for categories, brands, and acquirers.

## Scope

Does not process payments, issue invoices, or move funds. Use for reconciling card sales and reporting receivables through Destaxa only.

## Capabilities

- Retrieve sales details and summaries for a reconciliation period
- Chart how sales evolve over time
- Read a receivables calendar with summaries, details, and daily totals
- Break down receivables per sale and view consolidated totals
- List filter options for transaction categories, card brands, and acquirers

## Use cases

### Agent-Driven Reconciliation Reporting

An AI agent prepares a reconciliation report by pulling sales details and the receivables calendar for a period, then scoping both by acquirer and card brand using the filter endpoints. The agent returns daily totals and a consolidated view, so a finance assistant can show what was sold and what is still owed without opening the DTX Pro dashboard.

Example prompt: Retrieve sales details and the receivables calendar summary for a date range, filtered by a chosen acquirer, and return the daily totals

### Receivables Forecasting

Project upcoming cash flow by reading the receivables calendar's daily totals and consolidated figures. A treasury tool can show when acquirer payouts are expected and how much, turning the reconciliation data into a forward view of receivables.

Example prompt: Read the receivables calendar daily totals for the next 30 days and return the expected payout per day

### Filter-Scoped Analytics

Drive dashboards that slice sales and receivables by transaction category, card brand, and acquirer. The filter endpoints list the valid options first, so an analytics tool offers only real choices before requesting the matching sales or receivables data.

Example prompt: List the available acquirers and card brands, then pull the sales summary scoped to one acquirer

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/sales/details` | Sales details for a period |
| POST | `/sales/details/summary` | Sales details summary |
| POST | `/sales/analytics/evolution-graph` | Sales evolution over time |
| POST | `/receivables/calendar/summary` | Receivables calendar summary |
| POST | `/receivables/calendar/daily-totals` | Daily receivables totals |
| POST | `/receivables/calendar/consolidated` | Consolidated receivables view |
| POST | `/filters/acquirers` | List acquirers to filter by |
| POST | `/filters/brands` | List card brands to filter by |

## Key resources

- **Sales** — Sales details, summaries, and an evolution graph over time
- **Receivables** — Receivables calendar: summary, details, daily totals, per-sale breakdown, and consolidated views
- **Filters** — Available transaction categories, card brands, and acquirers to scope a query

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 0 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 58 / 100
  - AI-Readiness & Agent Experience: 29 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 0 / 100
- **View full report:** https://jentic.com/apis/destaxa.com/destaxa/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** By hand you obtain a JWT bearer token, set the Authorization header, learn the sales and receivables report shapes, and fetch filter options before a query returns the right slice. Through Jentic you connect once from the API Directory and your agent calls the reports by intent.
- **Permission scoping:** Every operation reads reconciliation data, so you grant your agent only the reports it needs, such as sales summaries and receivables totals while leaving out per-sale breakdowns. Every call is logged for audit.
- **Credential handling:** Your JWT bearer token is stored encrypted on your own Jentic One instance and injected into the Authorization header at execution time, never placed in the agent's prompt, logs, or context. You rotate or revoke it in one place.
- **Discovery method:** Agents search Jentic by intent such as 'receivables calendar summary' or 'sales details', and Jentic returns the matching Destaxa operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Adyen Checkout Service** — Processes the card payments whose settlements Destaxa reconciles.
- **Stripe** — A payment source whose card sales can be cross-checked against reconciliation reports.
- **Xero Accounting API** — Post reconciled sales and receivables figures into the accounting ledger.
- **Sage** — An accounting platform with its own reconciliation and reporting features.

## FAQ

### What authentication does the Destaxa DTX Pro API use?

It uses an HTTP bearer token in JWT format: every request carries a bearer credential in the Authorization header. Through Jentic, your own Jentic One instance stores that token encrypted and attaches it to each call rather than exposing it to the agent.

### Can I scope reconciliation data to one acquirer or card brand?

Yes. The filter endpoints list the available transaction categories, card brands, and acquirers, and you pass those values when requesting sales or receivables data. That lets a report cover a single acquirer, a single brand, or the whole account.

### What are the rate limits for the Destaxa DTX Pro API?

The OpenAPI spec does not state rate limits. Check the official Destaxa documentation at https://destaxa.com/ for current limits before pulling large reconciliation reports.

### How do I pull reconciliation data through Jentic?

Add the Destaxa DTX Pro API from the Jentic API Directory and connect your token once. Your agent then searches by intent such as 'receivables calendar summary' and calls the matching operation. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit which Destaxa operations my agent is allowed to call?

Yes. Every operation reads reconciliation data, so you grant your agent only the reports it needs, such as sales summaries and receivables totals while leaving out the rest. Every call the agent makes is logged, so you can audit exactly which reports it ran.

### Is there a Destaxa DTX Pro MCP server?

You don't need an MCP server to use Destaxa DTX Pro with your agent. Jentic connects it directly from the API Directory: import it, connect your token once, and your agent can pull sales and receivables data without another server loading tool definitions into its context.