Install Jentic One Beta

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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmoneris.io%2Fmoneris" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmoneris.io%2Fmoneris" | 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.

Create a card payment with automaticCapture, then complete or cancel a held authorization

Issue a matching refund against a paymentId or an independent refund to a payment method

Store, update, and delete reusable payment methods and customer profiles

Bill RECURRING subscriptions and pause, resume, extend, or cancel them by subscription ID

Run 3-D Secure card lookups and authentications before charging a card

GET STARTED

Start building with Moneris API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Moneris API for, with concrete tasks.

★ AI billing agent that charges and refunds through Moneris

An agent handling customer billing needs to take a payment or issue a refund without a developer wiring OAuth scopes, the X-Merchant-Id header, and idempotency keys by hand. Through Jentic the agent searches for 'refund a card payment', loads the Moneris refund operation with its input schema, and sends the paymentId and amount. Your own Jentic One instance injects the credential at call time, so the agent handles only the order data.

Call POST /refunds with an idempotencyKey, the paymentId of order 10423, and a partial amount, then confirm the refund status with GET /refunds/{refund-id}

Authorize now, capture at shipment

Merchants that ship physical goods often authorize a card at checkout and capture only when the order leaves the warehouse. The Moneris API creates the payment with automaticCapture turned off, then completes it with an amount at shipment time or cancels it with a reason if the order is cancelled. Every write takes an idempotencyKey so a retried call does not double-charge.

Create a payment with POST /payments using an idempotencyKey, paymentMethod, amount, and automaticCapture false, then call POST /payments/{payment-id}/complete with the final amount when the order ships

Recurring subscriptions with pause and resume

Subscription businesses on Moneris bill customers on a schedule using the RECURRING subscriptionType with billingDetails and a stored payment method. Subscriptions can be updated with PATCH, paused for a customer on a break, resumed, extended, or cancelled, and listed for reporting. This keeps the billing schedule on Moneris rather than in a separate scheduler.

Call POST /subscriptions/{subscription-id}/pause for subscription sub_8812 with an idempotencyKey, then call POST /subscriptions/{subscription-id}/resume on the requested return date

Fraud screening before charging

Card-not-present merchants screen risky orders before charging. The Moneris API runs a 3-D Secure card lookup and authentication for the cardholder, and submits a Kount inquiry with the order, billing address, products, and kountAccountId. After review, the assert operation records the merchant's decision on the inquiry.

Call POST /three-d-secure/card-lookups with an idempotencyKey, paymentMethod, and threeDSecureNotificationUrl, then POST /three-d-secure/authentications with the returned cardLookupId and the order amount

Key Endpoints

46 endpoints — the moneris api processes card payments for moneris merchants, from authorization and capture through cancellation and refunds.

METHOD

PATH

DESCRIPTION

POST

/payments

Create a payment

POST

/payments/{payment-id}/complete

Capture an authorized payment

POST

/refunds

Create a refund

POST

/payment-methods

Store a payment method

POST

/subscriptions

Create a subscription

POST

/subscriptions/{subscription-id}/pause

Pause a subscription

POST

/three-d-secure/authentications

Create a 3-D Secure authentication

POST

/kount-inquiries

Create a Kount fraud inquiry

POST

/payments

Create a payment

POST

/payments/{payment-id}/complete

Capture an authorized payment

POST

/refunds

Create a refund

POST

/payment-methods

Store a payment method

POST

/subscriptions

Create a subscription

POST

/subscriptions/{subscription-id}/pause

Pause a subscription

POST

/three-d-secure/authentications

Create a 3-D Secure authentication

POST

/kount-inquiries

Create a Kount fraud inquiry

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Moneris API by hand means choosing between OAuth 2.0 client credentials and an X-Api-Key, requesting the right scopes per resource, and sending X-Merchant-Id, Api-Version, and an idempotencyKey on every write. Through Jentic you install once, import Moneris from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Moneris puts resource IDs in the URL path, such as /subscriptions/{subscription-id} and /onboarding/merchants/{merchant-id}, so a rule can hold your agent to one subscription or merchant and the operations you pick. You choose the operations it may call, so destructive ones like deleting a customer or cancelling a payment are not included unless you add them.

Credential isolation

Your Moneris client credentials or API key are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'refund a card payment' or 'pause a subscription', and Jentic returns the matching Moneris operation with its input schema, including required fields like idempotencyKey and paymentMethod.

FAQs

Specific to using Moneris API through Jentic.

What authentication does the Moneris API use?

Per its OpenAPI spec, the Moneris API accepts two schemes: OAuth 2.0 client credentials with scopes such as payment.write, refund.read, and customer.write, or an API key sent in the X-Api-Key header. Moneris recommends OAuth 2.0 for its finer scopes. Requests also carry the X-Merchant-Id and Api-Version headers. Through Jentic the credential is stored by your own Jentic One instance and attached at call time.

Can I issue a partial refund with the Moneris API?

Yes. POST /refunds accepts a matching refund that references the original paymentId, or an independent refund sent to a stored paymentMethod. Set the amount to refund part of the payment, and check the result with GET /refunds/{refund-id}.

What are the rate limits for the Moneris API?

The OpenAPI spec does not specify rate limits. Check the Moneris developer portal at https://developer.moneris.com for current limits on your merchant account, and use the sandbox host at api.sb.moneris.io for testing.

Is there a Moneris MCP server?

You don't need an MCP server to give your agent the Moneris API. Jentic connects it directly from the API Directory: import it, store your OAuth client credentials or API key once, and your agent calls the payment, refund, and subscription operations on demand without loading another server's tool definitions into its context.

Can I limit what my agent is allowed to do with the Moneris API?

Yes. Write a rule that allows only GET /payments, GET /payments/{payment-id}, and POST /refunds, so a support agent can look up a charge and refund it but cannot create new payments, delete customers, or onboard merchants. Every call it makes is logged.

How do I pause a subscription through Jentic?

Search Jentic for 'pause a Moneris subscription', load the POST /subscriptions/{subscription-id}/pause operation, and execute it with the subscription ID and an idempotencyKey. Resume it later with POST /subscriptions/{subscription-id}/resume. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Moneris API

Browse all Moneris APIs

AI ReadinessAI-Aware (A-)71/100

See full scorecard

Community OpenAPI document · agent-readyPaymentsPayment Processingoauth2, apiKey46 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Take card payments, capture or cancel them, issue refunds, store payment methods, and bill recurring subscriptions for a Moneris merchant, with 3-D Secure and Kount fraud checks.

Use for: I need to charge a customer's card for an order, Capture a payment that was authorized earlier, Refund part of a payment to the original card, Set up a recurring subscription for a customer

Not supported: Does not handle loyalty points, payroll, or accounting ledgers. Use for Moneris card payments, refunds, subscriptions, and merchant onboarding only.

The Moneris API processes card payments for Moneris merchants, from authorization and capture through cancellation and refunds. It stores payment methods and customer profiles, runs card validations, and bills recurring subscriptions that can be paused, resumed, extended, or cancelled. 3-D Secure card lookups and authentications, Kount fraud inquiries, and installment plan lookups support riskier or larger card-not-present sales. Merchant onboarding operations create merchants, place equipment and supply orders, and return product recommendations.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: CSignals: 4

91%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

30%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

41%

Example Density

How richly the API is illustrated with examples.

98%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: B+Signals: 4

91%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

78%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B+Signals: 1

68%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

66%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Moneris API to your agent

Capabilities

Start building with Moneris API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Moneris API

Jentic AI Readiness Score

Moneris API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness