Additional Features

A credit card payment moves through many steps from the cardholder offering their card as the method of payment all the way to the merchant receiving funds in their bank account. Use the guide below to better understand each phase in card payment.

1. Payment Methods

The Unified API offers the Payment Method resource for storing customer payment details essential to processing transactions. By storing a Payment Method, merchants can bill customers for routine products or services when the invoice is due without reacquiring the payment details, both increasing security and faster checkout experience for the customer. Alternatively, merchants may create a payment method “on the fly” within many Moneris API endpoints, processing their transaction in a single call.

Moneris supports the following payment methods

  • CARD – Credit or debit cards issued by a bank. Cards are the most common payment method and many alternative payment methods are built from underlying card data secured in some manner.

  • TEMPORARY TOKEN – A token returned from the Moneris Hosted Tokenization feature. Tokenization of card data with Moneris provides additional security to the merchant server, as your systems never touch card data directly.

  • PERMANENT TOKEN – A token returned from the Moneris Vault service. If a merchant is already integrated with Classic Moneris Gateway, you may already have a repository of Vault tokens (data keys) stored with Moneris. The Moneris Unified API allows a merchant to continue processing with these permanent tokens or convert them into Payment Method IDs instead.

  • WALLET – Digital wallets allow customers to streamline payment processing by storing their payment method securely with a third-party for use across mobile devices and web-browsers. Afterward, the customer makes payments with confidence in merchant applications or eCommerce websites.

    The Moneris API supports the following digital wallets:

  • Apple Pay, In-App

  • Apple Pay, On The Web

  • Google Pay, In-App

    For instructions on integrating your merchant solution to utilize digital wallets, consult our guides for Apple Pay and Google Pay integration.

2. Storing Payment Methods

The Unified API offers the Payment Method feature for storing customer payment details essential to processing transactions. This allows merchants to bill customers for routine products or services when the invoice is due without reacquiring the payment details, both increasing security and faster checkout experience for the customer.

3. Storing Customer Details

The Unified API offers the Customer resource for creating and editing customer profiles. These profiles store non-payment related details, such as a customer’s email address or phone number, within Moneris systems

4. 3D Secure Authentication

3-D Secure 2.2 is an EMVCo payment authentication protocol designed to reduce card not present fraud by making a risk assessment based on transaction and device data, while also supporting further risk minimization measures, such as a challenge to the cardholder. In some cases, a liability shift takes effect for certain card-not-present fraud-related chargebacks enabling the merchant to provide goods and services with confidence.

The Moneris Unified API can enable transactions using the 3-D Secure protocol via Moneris 3DS Server and access Control Server (ACS).

Moneris supports the following 3-D Secure implementations:

  • Visa Secure

  • Mastercard Identity Check

  • American Express SafeKey

5. Risk Inquiry with Kount

Kount is a third-party fraud prevention service that assesses the risk of your transactions. Automatic risk scoring and predictive modeling is used to ensure confidence that your business can go forward with transactions that match your risk profile, proactively preventing chargebacks.

An integration with Kount involves two major components to compose a risk score:

  • Data Collector is how Kount gathers technical information on your customers device, software, and IP address. This process runs directly between your merchant website and the Kount servers with no pass-through via Moneris API.

  • Risk Inquiry Service is how a merchant submits all other information used in the risk score, such as the customer’s card information, contact details, and shipping/billing address. You can use our Moneris API endpoints under the Kount resource to create or update a risk inquiry.

Moneris offers two types of Kount service:

  • Kount Essentials utilizes a pre-defined risk profile generated by Moneris based on the typical needs of your business type. With Kount Essentials, you do not need to establish a separate account for Kount; Moneris generates Kount credentials on your behalf.

  • Kount Enterprise allows a merchant to fully customize their risk profile with Kount directly. When it is time to move your solution into production, you will need to consult your Kount Client Success Manager to obtain Kount credentials.