# Finexio API Contract Snapshot

Planning artifact. Confirm production values, schemas, required fields, event names, credentials, and environment behavior in the current Finexio Developer Hub before build or launch.

## Contract Owners

- Buyer/AP owner: payment approval, policy, source-system data, and production authorization.
- Finexio implementation: onboarding scope, tenant setup, payment workflow, supplier operations, and production handoff.
- Engineering owner: API client, file transfer, webhook consumer, polling, logging, retry behavior, and alerting.
- Accounting/treasury owner: funding, drawdown, reconciliation, close timing, and downstream ledger updates.

## Environments And Access

- Confirm sandbox and production base URLs during credential issuance.
- Store credentials in an approved secret manager.
- Define credential owner, rotation process, access revocation, and go-live handoff.
- Validate sandbox access before building payment workflows.
- Use non-production buyer, supplier, invoice, and payment data in sandbox.

## Integration Surfaces To Scope

| Surface | Planning Purpose | Source Of Truth |
| --- | --- | --- |
| Counterparties | Validate credentials and understand buyer/supplier records | Developer Hub |
| Invoice batches | Submit approved invoice/payment instructions | Developer Hub |
| Payments | Poll current payment status and details | Developer Hub |
| Webhooks | Receive prompts to fetch changed payment records | Developer Hub |
| Reconciliation drawdown | Match funding, payment, invoice, and supplier records | Developer Hub |
| File exchange | Support file-first or hybrid implementation paths | Finexio implementation |

## Required Design Decisions

- System of record for buyer, supplier, invoice, payment, and reconciliation identifiers.
- Idempotency strategy for repeated file, API, webhook, or polling events.
- Status values consumed by AP, treasury, support, accounting, and suppliers.
- Webhook verification, retry handling, dead-letter queue, and alerting owner.
- Polling cadence and fallback behavior when webhook delivery is delayed.
- Exception states that should pause, reopen, reverse, reissue, or hold downstream records.
- Reconciliation fields required to close the AP run.

## Launch Tests

1. Validate sandbox credentials and log the owner of each credential.
2. Submit representative approved invoice/payment data.
3. Poll payment records and map each status to a downstream action.
4. Register a webhook subscription and confirm repeated notification handling.
5. Compare reconciliation output against the source AP run.
6. Test exception, return, reissue, and support escalation handling.
7. Confirm production cutover owner, launch window, rollback path, and support routing.

## Go/No-Go Evidence

- Signed-off file/API field map.
- Status and webhook handling matrix.
- Reconciliation sample accepted by accounting/treasury.
- Security review complete for credentials, transfer, logging, and support access.
- Buyer support and supplier support routing confirmed.
- Finexio implementation owner and customer technical owner named for launch.