Overview

Technologies

To use Hosted Tokenization, your system must include a web server capable of sending and receiving HTTP POST/GET requests.

You need the following skills:

• Ability to create HTML pages, iframes, and form submissions.
• If you sell more than one item, familiarity with a client-side scripting language (for example, JavaScript or PHP) to calculate a final charge amount.
• If you want to generate custom receipts and perform transaction verification, familiarity with a server-side scripting language (for example, PHP, Perl, or ASP).

Process Flow

When a Hosted Tokenization transaction is initiated, the Moneris Gateway renders a secure payment input field on the merchant checkout page. The cardholder enters card data directly into this field. After submission, the gateway returns a temporary token that represents the card number.

The merchant then uses this token in an API request to process the financial transaction through Moneris. After receiving the transaction response, the merchant can generate a receipt and continue the checkout flow.

The following diagram outlines the process flow, along with a description of each step below it.

1. The Consumer shops at a merchant site with their web-browser and proceeds to the checkout page.
2. The checkout page is presented by the merchant's server with Hosted Tokenization integration.
3. An iframe within the merchant checkout page loads Moneris Hosted Tokenization configuration.
4. The cardholder enters card data and any additional payment-related information required by the merchant. When the cardholder selects Submit, the checkout page code sends a request to the Moneris Gateway to obtain a temporary token representing the card data. The checkout page then sends the token and other payment-related data to the merchant endpoint selected to collect this information.
5. The merchant server sends a Vault transaction to Moneris using the payment information received in step 4. The merchant saves the Vault transaction response for reference. For more information refer to the Vault API documentation.
6. The transaction result is displayed to the cardholder.