canonical: https://jentic.com/apis/moneris.com/moneris # Moneris API Jentic publishes the only available OpenAPI specification for Moneris API, keeping it validated and agent-ready. Moneris is a Canadian payment processor offering e-commerce card acceptance for merchants. The minimal API exposed here covers the three core transaction primitives every Canadian merchant needs: a one-step purchase, a refund against a prior transaction, and a pre-authorisation that can be captured later. Authentication is an API key passed in the Authorization header. ## For AI agents Authorise, capture, and refund Canadian card payments through Moneris using three POST endpoints for purchase, preauth, and refund. ## Scope Does not handle subscriptions, payouts, tokenisation vaults, or in-person terminals - use for online Canadian card purchase, pre-authorisation, and refund only. ## Capabilities - Charge a card in a single step by posting amount, order id, and card details to /purchase - Authorise funds without capturing by calling /preauth so the sale can be completed later - Refund all or part of a settled Moneris transaction by referencing the original order id on /refund - Reconcile each transaction by storing the Moneris response code returned with every successful call - Operate in CAD against Canadian-issued cards on the moneris.com acquiring rails ## Use cases ### Canadian E-Commerce Checkout A Canadian online store sends each completed cart to POST /purchase with the order total, order id, and tokenised card data, and reads the Moneris response code to mark the order paid. The same flow handles partial refunds via /refund when a customer returns an item, all without leaving the Canadian acquiring rails or paying cross-border interchange. Example prompt: Send a 119.99 CAD purchase to Moneris with order id ORD-2025-001 and confirm the approval response code. ### Auth-Then-Capture for Shipped Goods Retailers that only charge on shipment authorise the card with POST /preauth at order time, then complete the sale once the parcel leaves the warehouse. This avoids charging for backordered items and reduces refund volume, since the funds are released automatically if the preauth is never captured. Example prompt: Pre-authorise 250.00 CAD on a customer card via /preauth and store the order id for capture when the order ships. ### Refunds and Reversals Customer service tools call POST /refund with the original order id and the amount to credit back when a buyer returns goods. Moneris reverses the funds on the same card and returns a response code that the merchant records against the original transaction for accounting reconciliation. Example prompt: Refund 49.99 CAD against Moneris order ORD-2024-9912 and log the returned response code. ### AI Agent Canadian Payment Operations An agentic checkout workflow uses Jentic to discover Moneris purchase, preauth, and refund operations, loads their schemas, and runs them with vault-injected credentials. Because Moneris does not publish a public OpenAPI spec, Jentic's spec is the only structured way for an agent to call this API without scraping the developer portal. Example prompt: Search Jentic for 'process a Canadian card payment', load the Moneris purchase schema, and execute a 50 CAD test charge. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/purchase` | Process a one-step purchase | | POST | `/preauth` | Pre-authorise funds on a card | | POST | `/refund` | Refund a prior transaction | ## Key resources - **Transactions** — Process purchases, pre-authorisations, and refunds against Canadian-issued cards ## Why Jentic - **Setup:** Wiring the Moneris API by hand means setting the Authorization API-key header and coding the purchase, pre-authorisation, and refund calls for Canadian card processing yourself. Through Jentic you install once, import the Moneris API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Moneris carries the card and transaction detail in the request body rather than as a path resource, so you limit the agent to the operations it needs, such as a purchase or pre-authorisation. You choose the operations it may call, so one like issuing a refund is not included unless you add it. - **Credential handling:** Your Moneris key is stored once, encrypted, by your own Jentic One instance and injected at execution time, even when the agent serves multiple Canadian merchants. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'process a Canadian card payment', and Jentic returns the matching Moneris purchase, preauth, or refund operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Stripe API** — Global processor with native CAD support and a far broader feature surface - **Square API** — Canadian-supported processor with strong in-person and online integrations - **Braintree API** — PayPal-owned gateway with multi-currency support and richer wallet integrations - **PayPal Payments API** — Add PayPal wallet alongside Moneris card processing on Canadian storefronts ## FAQ ### Why is there no official OpenAPI spec for Moneris API? Moneris does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Moneris API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Moneris API use? An API key passed in the Authorization header. Through Jentic the key is stored encrypted in the credential vault and injected at execution time, so the agent never sees the raw secret value. ### Can I do auth-and-capture with the Moneris API? Yes. Call POST /preauth with the amount and order id to place a hold, then later capture the funds. The /purchase endpoint is the one-step alternative that authorises and captures in a single call. ### What are the rate limits for the Moneris API? The spec does not declare explicit rate limits. Treat 429 responses as a back-off signal and retry with exponential delay. Production volumes are typically negotiated with Moneris as part of the merchant agreement. ### How do I refund a Moneris transaction through Jentic? Search Jentic for 'refund a Canadian card payment', load the schema for POST /refund, and execute it with the original order id and refund amount. Jentic handles the Authorization header so only the business inputs are needed. ### Does the Moneris API support partial refunds? Yes. POST /refund accepts an amount that can be less than the original purchase, allowing partial refunds. Each refund returns a response code that should be stored against the original order id for reconciliation. ### Can I limit what my agent is allowed to do with the Moneris API? Yes. Because you run Jentic One yourself, your own rules decide which Moneris operations the agent may call, so you can grant it POST /purchase and POST /preauth for taking payments while withholding POST /refund. Since Moneris carries the card and transaction detail in the request body rather than as a path resource, scoping is done at the operation level: the agent can only reach the endpoints you have imported and enabled for it. Any operation you do not add, such as issuing a refund, stays unavailable to the agent, and the encrypted API key is injected only when it runs one of the operations you allowed.