> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gr4vy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Moneris - Card

> Connect to Moneris to accept card payments.

Moneris is a leading payment processor in Canada, offering comprehensive payment
processing solutions for businesses across North America. Moneris provides secure
card payment processing for Canadian and US merchants.

## Setup

Registration for Moneris is available through [their
website](https://api-developer.moneris.com/signin).

## Connector configuration

After signing up with Moneris, you can configure the connector in Gr4vy using
one of the following methods:

* **[Flow](/guides/dashboard/flow)** - Configure payment routing rules through
  your Gr4vy dashboard
* **[API integration](/guides/payments/direct-api/quick-start/overview)** - Specify the
  `payment_service_id` when creating transactions to explicitly route payments
  to this connector

## Credentials

Configure the following credentials in the Gr4vy dashboard, which are obtained
from your Moneris developer portal:

* **Merchant ID** - Your unique merchant identifier
* **Client ID** - Your API client identifier
* **Client Secret Key** - Your API client secret for authentication

## Features

Moneris supports the following features:

* **Delayed capture** - Authorize a payment and capture it at a later time
* **Partial capture** - Capture a portion of the authorized amount
* **Partial refunds** - Refund a portion of the captured amount
* **Refunds** - Refund a captured payment
* **Void** - Cancel an authorized transaction before capture
* **Zero auth** - Verify a card without charging it
* **Digital wallets** - Support for Apple Pay, Google Pay, and other wallet
  integrations
* **Transaction sync** - Synchronize transaction status with Moneris
* **3-D Secure** - Pass-through 3DS authentication

## Supported countries

Moneris supports transactions from buyers in `CA` and `US`.

## Supported currencies

Moneris supports processing payments in `CAD` and `USD`.

## Limitations

The following features are not supported by this connector:

* **Create session** - Session creation is not supported
* **Network tokens** - Network tokenization is not supported
* **Open loop** - Open-loop card processing is not supported
* **Over capture** - Capturing more than the authorized amount is not supported
* **Partial authorization** - Partial authorization is not supported
* **Payment method tokenization** - Storing payment methods outside of
  transactions using a separate tokenization flow
* **Settlement reporting** - Automatic settlement reporting is not supported

Additional limitations include:

* **CVV required for all transactions** - The CVV is mandatory for all
  transactions, including merchant-initiated transactions (MIT), due to a known
  issue in the Moneris API.

<Note>
  This is a closed-loop connector. Some failover scenarios are limited.
  For details, see [Open loop versus closed loop](https://docs.gr4vy.com/guides/features/recurring-payments/open-loop#open-loop-versus-closed-loop).
</Note>

## Integration

To accept card payments with Moneris, use one of Gr4vy's client-side integration
methods to securely collect card details. Due to PCI compliance requirements,
card data should never be sent directly to your servers.

You can integrate using:

* **[Embed](/guides/payments/embed/quick-start)** - A pre-built, customizable
  payment form that handles the complete payment flow
* **[Secure Fields](/guides/payments/secure-fields/quick-start)** - Embed card
  input fields for building custom payment forms while maintaining PCI
  compliance
* **[Mobile SDKs](/guides/get-started#sdks-and-plugins)** - Native SDKs for iOS,
  Android, React Native, and other platforms

These methods handle card data collection and tokenization. Once the card
details are collected and tokenized, create a transaction through the Gr4vy API,
which routes the payment to your configured Moneris connection based on your
Flow rules or explicit `payment_service_id` parameter.