Account creation, status changes and the four standard reports sit behind a single API key, and the plan on that key decides how far a conversation can go - so a read-only key and a full one are the same integration with different reach.
A FastMCP server exposing the creditor-facing side of the FixPayment portal. Every call carries an API key, and the plan that key maps to - basic, reports or full - decides which of the twelve tools answer.
- New creditor accounts created one at a time or in bulk
- An account's status moved
- A document attached to an account
- A payload checked before you commit it
- Account summaries and a basic account listing
- Four reports - accounts, payments, settlements and performance
- The plan your key is on, read back
A FixPayment API key, passed as an argument on every tool call. The key maps to one plan and the plan gates the tools: basic covers the summary and listing calls, reports adds the four report tools, full adds account creation and status changes. If a tool will not answer, read the plan back first. Self-hosting instead of using the published endpoint also needs PostgreSQL, the five FIXPAYMENT_DB_ variables and an upload directory.