Moneris API

Name: Moneris API API
Brand: Moneris API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment ProcessingapiKey3 EndpointsREST

For Agents

Authorise, capture, and refund Canadian card payments through Moneris using three POST endpoints for purchase, preauth, and refund.

Connect the Moneris API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Moneris API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Moneris API API.

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

GET STARTED

Start building with Moneris API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Moneris API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Moneris API API for, with concrete tasks.

★ 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.

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.

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.

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.

Search Jentic for 'process a Canadian card payment', load the Moneris purchase schema, and execute a 50 CAD test charge.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for moneris api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/purchase

Process a one-step purchase

POST

/preauth

Pre-authorise funds on a card

POST

/refund

Refund a prior transaction

POST

/purchase

Process a one-step purchase

POST

/preauth

Pre-authorise funds on a card

POST

/refund

Refund a prior transaction

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Moneris API keys are stored encrypted in the Jentic vault. The Authorization header is set at execution time so the raw key never enters the agent's context, even when the same agent serves multiple Canadian merchants.

Intent-based discovery

Agents search Jentic by intent (e.g. 'process a Canadian card payment') and receive the matching Moneris purchase, preauth, or refund operation with its full input schema.

Time to first call

Direct Moneris integration: 1-3 days reading developer portal docs and wiring purchase, preauth, and refund flows. Through Jentic: under 1 hour to search, load the schema, and execute the first live transaction.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Stripe API

Global processor with native CAD support and a far broader feature surface

Choose Stripe when the merchant wants subscriptions, Connect, or non-card methods rather than bare Canadian card processing.

Alternative

Square API

Canadian-supported processor with strong in-person and online integrations

Choose Square when the merchant runs both an online store and physical Square terminals and wants one platform across both.

Alternative

Braintree API

PayPal-owned gateway with multi-currency support and richer wallet integrations

Use Braintree when the merchant needs PayPal or Venmo alongside CAD card acceptance.

Complementary

PayPal Payments API

Add PayPal wallet alongside Moneris card processing on Canadian storefronts

Pair with Moneris when the merchant wants PayPal as an additional checkout option for Canadian and US shoppers.

FAQs

Specific to using Moneris API API through Jentic.

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 at https://app.jentic.com/sign-up.

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.