---
updatedAt: 2026-09-09T01:56:57.000Z
---
# Overview
Hosted Tokenization is a secure ecommerce solution that enables merchants to bypass direct handling of credit card data while maintaining full design control over the checkout experience.
Moneris Hosted Tokenization enables you to securely accept payments without routing sensitive credit card data through your own servers, while retaining complete control over your checkout page's UI.
Because raw cardholder data is tokenized directly by Moneris and is never captured or stored by your application, integrating this solution significantly reduces your PCI compliance assessment scope.
If you prefer a fully managed, drop-in payment page rather than building a custom UI, refer to the [Hosted Checkout](hosted-checkout-introduction) documentation.
## 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. **Consumer navigates to the merchant site**:
The consumer shops at a merchant site with their web-browser and proceeds to the checkout page.
2. **Merchant presents the checkout page**:
The checkout page is presented by the merchant's server with Hosted Tokenization integration to the consumer.
3. **Merchant loads the Moneris Tokenization iframe**:
The checkout page loads the Moneris Hosted Tokenization iframe based on the merchant's configuration.
4. **Checkout page retrieves the token from Moneris**:
The cardholder enters their card data. When the cardholder selects **Submit**, the checkout page posts a message to the Hosted Tokenization iframe, which triggers a request to the Moneris Gateway to obtain a temporary token representing the card data.
5. **Checkout page sends checkout details to merchant:**
The checkout page then sends the token and other payment-related data to the merchant endpoint selected to collect this information.
6. **Merchant completes payment with Moneris**:
The merchant server sends a Vault transaction to Moneris using the payment information received in step 5. The merchant saves the Vault transaction response for reference. For more information refer to the [Vault API documentation](https://legacy-developer.moneris.com/Documentation/NA/E-Commerce%20Solutions/Hosted%20Solutions/~/link.aspx?_id=DA303DE370864B50BC167309D103EB6C&_z=z).
7. **Merchant presents results to consumer**:
The transaction result is displayed to the cardholder.