ECPay
ECPay
System integration
Lets the Agent look up ECPay e-invoices and, when asked, resend, issue, or void them with one shared set of API keys.
Connection routes
About the routes →FDE Rune
API key or tokenWhile the deployment is being designed, the FDE Agent first looks at the e-invoice setup: number ranges, carrier types in use, and recent invoices
Workspace Connector
API key or tokenOnce live, the Agent looks up and manages e-invoices with one shared set of ECPay API keys (e.g. an organization's merchant account); issuing and voiding wait for the user to allow them on the platform's approval prompt
Documentation
Lets Asgard Agents look up ECPay B2C e-invoices by invoice number or order number, check their status, and resend the invoice notice to the buyer. When asked, they can also issue an invoice or void one; the platform shows the user what will be sent and waits for them to allow it.
ECPay payments and logistics are not in this version.
What you need
- Access to the ECPay merchant backend with the e-invoice service enabled, to copy the e-invoice API keys (the FDE Agent walks you through it step by step)
- What the Agent may do besides looking up invoices (resend, issue, void), so only those tools are built
Rollout consultation
ECPay is a trademark of its owner.