Hosted Payments Admin Dashboard

The Admin Dashboard enables you to configure payment options, customize the payment page, view transaction history, and handle minor exception processing such as issuing refunds, unlocking accounts, and more. You can access the merchant dashboard by visiting here: https://hostedpayments.merchante.com/hpp/admin/sign-in

The Setting and Configuration tab allows you to set up payment options and manage the URLs needed to make your payment page fully functional.

Open

Apple Pay offers a simpler and more secure alternative to using physical credit, debit, or prepaid cards. It allows you to accept payments in stores, apps, or on the web using built in hardware and software security features to make these payments easily, securely, and privately.

 MerchantE can facilitate the processing of transactions using Apple Pay directly from your website using the Payment Gateway or by using a Hosted Payment Page. This document outlines the process for submitting payments directly to the Payment Gateway.

Adding a Payment Card to Apple Wallet

When a customer creates an Apple Wallet account, payment methods must be added to wallet to make purchases. The diagram below shows the process which enables a payment method in Apple Wallet.

Open

1. Customer adds the physical card number (FPAN) to Apple Wallet.

2. Apple Wallet coordinates with the card network to validate the customer.

3. The DPAN is generated and added to the iPhone secure element. The DPAN from the iPhone secure element is then used for Apple Pay transactions.

Making a Purchase using Apple Pay

Once payment methods have been added to Apple Pay, the method can be used to make purchases from Apple Pay compliant merchants. The diagram below shows the transaction processing when a purchase is made using Apple Pay.

1. Biometric authentication is used to verify the customer.

2. The Apple Pay servers encrypt the DPAN from the secure element to generate a payment token.

3. The payment token is sent to the Merchant or the Hosted Payment Portal. If using the Payment Gateway directly, the payment token must be decrypted.

4. The transaction information is sent to MerchantE.

5. The Merchant receives the verification and completes the transaction.

6. Apple Wallet is notified of the approved transaction.

When a user purchases goods or services from your website, PassKit (mobile) or Apple Pay JS (Safari) determines they are using a qualified device. If they are using a qualified device, the Apple Pay button will appear as one of the payment options.

 If the customer selects Apple Pay as the payment method, they are immediately presented with the Payment Sheet. The Payment Sheet will present the customer with their stored payment options. This includes the card payment option and address.

Once the customer has selected a payment option and authorizes the request using a linked device, a payment request is created. If authorization succeeds, a payment object is generated. The payment object contains all the customer data and the payment token.

The payment token is sent to the Merchant or the Hosted Payment Portal. If using the Payment Gateway directly, the payment token must be decrypted. The payment token contains:

• Device specific authorization number (DPAN)

• Payment amount

• One-time-use cryptogram

The payment token is then sent to the card issuer to complete the payment.

Google Wallet offers a simpler and more secure alternative to access all your essentials, such as payment cards, loyalty cards, concert tickets and more using your phone. The Google Pay API provides access to physical credit, debit, or prepaid cards that have been saved to Google. It allows you to accept payments in stores, apps, or on the web.

Adding a Card to Google Pay

1. The customer creates a Google Wallet account and adds payment methods to the wallet.

2. The payment methods are stored in Google Servers. A list of payment methods is provided when the service is invoked.

3. Google severs return payment payload when the payment method is used for a transaction. The payment payload is passed to MerchantE by the merchant for processing.

Making a Purchase using Google Pay

1. A customer checks out on the Merchant website and uses Google Pay as payment.

2. Google Pay is invoked and the available payment methods are provided. The encrypted payment payload and unencrypted details are provided.

3. The encrypted payment payload and transaction details are sent to the Merchant.

4. The payment payload is sent to MerchantE for decryption and processing. The transaction is executed and the results are sent to the Merchant.

5. The Merchant sends the transaction receipt to the customer.

The Custom Amount setting controls whether the customer will be able to enter an amount for the transaction or if the amount will be populated and locked by the merchant.

• When this feature is enabled, the merchant is giving the customer the ability to enter their payment amount.

• When the feature is disabled, the merchant is specifying the payment amount.

A payment card surcharge, also known as a checkout fee, is an additional percentage-based fee that a merchant adds to a transaction when a credit card is used for payment. You can add surcharges to credit card payments to offset the cost of processing the transaction. Surcharges are only valid for credit card transactions and cannot be applied to debit cards, prepaid cards, or ACH transactions.

Initiating Surcharges:

• The card brand must be notified 30 days in advance of beginning the surcharge. Consult the surcharge rules for each card brand accepted. On the registration forms, it is important that you list:

  • “MerchantE” as the “Acquirer/Payment Service Provider”

  • “Brand” as the “Type of Surcharge.”

    • Visa

    • Mastercard

    • Discover

• Some states prohibit surcharging. Consult your legal counsel to ensure that you are in compliance with relevant state laws. The table shows states and US territories where surcharging is prohibited or prohibited but unenforceable due to pending litigation (October 2022).

The Recurring Payment setting enables you to offer your customers the option to set up recurring payments. When this feature is enabled, you can establish whether your customers can select their preferred frequency, or you can limit the frequency options to only one (or a limited section of frequencies). Select one or more of the boxes to enable: weekly, bi-weekly, and monthly.

With the combination of Custom Amount and Recurring Payments, you can structure your payments option to meet your business needs. The following table illustrates the various combinations between the two payment options:

The Manage URLs section allows you to manage the various URLs needed to make your payment page fully functional.

Payment Page URL

The Payment Page URL will redirect your customer from your website to the Hosted Payment Page. Additional details on how to utilize this URL can be found in the Hosted Payments Implementation section.

Redirect URL

The Redirect URL is intended to redirect your customer back to your website. Upon successful checkout, your customer will have the option to be redirected to the URL specified in this field.

Advanced URLs Management

For most Hosted Payments integrations, the process stops after the customer submits their payment. However, there are some merchants who need additional information feed into their back-end systems. The settings in this section are optional and are intended for those who need advance integrations into the Hosted Payment Product. Additional details about how to utilize this section can be found in the Hosted Payments Implementation section.

The HPP Customization tab is the area where you can modify the look the of the Hosted Payments page that your customer sees to best reflect your brand. You can select a theme color, upload a logo, and add links to your company’s Terms of Service and Policy.

Background Color

The background color dictates the color of the background on the checkout related screens. You can select a theme color by picking a color box or you can enter the hex code. The color box allows you to modify the color and the opacity of the background.

Company Logo

You can upload your logo by clicking on the Upload Logo Files button. Your image must be PNG, JPG, or GIF format. The file size cannot exceed 265KB.

Footer

The footer will appear at the bottom of your payment page. It will display your company name and all rights reserved. Additionally, you can upload your Terms of Service Policy and your Privacy Policy to your payment page. When one or both links are provided, we add the links to the footer.

Theme Color

The theme color controls, links, transaction amount, buttons, and user icon of the payment page and the customer dashboard. You can select a theme color by picking a color box or you can enter the hex code.

On the Transaction History tab of the merchant dashboard, you can search for transaction(s), resend receipts, submit refunds or voids, and reset customer’s accounts. When you click on the tab, the page will display a list of your most recent transactions.

Each transaction is listed with:

• Customer Name

• Email Address

• Transaction ID

• Payment Method

• Date

• Result

• Transaction Amount

• Actions (a link to actions available)

You can sort any of these columns except for the email address. It is important to note here that sorting by Payment Method sorts by the entire card or account number, but the page only displays the last four digits for security purposes. When performing a search on this value, you should enter the last four digits of the card or account number. When you click on the Actions link, a drop-down menu will appear, displaying a range of actions you can select for that transaction:

On the User Management tab of the merchant dashboard, you can perform some basic troubleshooting on your users’ accounts as well as see the activation status of users registered to your Hosted Payments page. Users can be in one of three states:

• Active – Customer has completed the registration for HPP.

• Pending – Customer has begun the registration process but has not confirmed via email.

• Inactive – Customer has not logged into HPP recently

Customers that have not been actively using HPP and have become inactive can be reactivated using the Actions column.

The MerchantE Reporting Portal is provided to every merchant using ME Hosted Payments. The website address and login credentials are identical to regular Hosted Payments and are provided upon completion of the merchant application process.

 The Reporting Portal adds the following functionality to ME Hosted Payments:

• Exception processing. The Reporting Portal offers a wider variety of transaction types. In addition to a sale, merchants can process Pre-Authorizations, Refunds, Voids, and Offline transactions.

• View Unsettled Transactions. Merchants can view in real time, transactions which have been processed since the last batch close.

• View Rejected Transactions. Like Unsettled Transactions, merchants can view rejected or declined transactions, including a description of why the transaction failed.

 The administrative section allows for customization of settings such as:

• Modification of the batch close time.

• Settings to decline transactions with certain Address Verification results, such as a “no ZIP match” even if the request receives an authorization code.

• Settings to decline transactions with certain Card Security Code results, such as “P” for not processed even if the request receives an authorization code.