HPCI Announcements

iFrame V5

December 01, 2020

What is iFrame V5?

iFrame V5 is the latest version of the HostedPCI iFrame which is available to the merchants. iFrame V5 has few new features such as a Masking feature for credit card numbers and CVV which masks the credentials entered on the iFrame. It also has ‘waitbin’ feature available which is initiated by a parameter in the iFrame SRC. iFrame V5 also includes the features which were available in the previous version of the HostedPCI iFrame.

How can it benefit you?

The benefit of iFrame V5 is that it ensures the merchants have the latest iFrame with the up to date features and support. Since it also includes all of the features from previous iFrame versions the merchants are able to use a feature that was released in the past as well.

Additional Resources:

3D Secure 2.0

September 01, 2020

What is 3D Secure 2.0?

HostedPCI has implemented 3DS 2.0 to align with the latest SCA requirements which were released in 2018 and must be in full effect by the end of 2020. 3D Secure 2.0 protocol relies on multi-factor authentication for eCommerce payment transactions in order to reduce fraudulent transactions. Merchant can use our 3D Secure 2.0 implementation with multiple different payment gateways, check out our gateway page for more details.

How can it benefit you?

The benefit to Merchants for implementing the new 3D Secure 2.0 mandate is a higher authorization rate and reduced chargebacks. Merchants also benefit from the liability shifts that occur when they invoke the 3DS challenge within their checkout page. To learn more about the benefits of using the new 3DS 2.0 feature visit our blog.

Credentials on File

September 02, 2020

What is Credentials on File?

Credentials on File is a mandate created for the Canadian eCommerce market in 2018, to reduce fraudulent transactions. Credentials on File works by tagging each transaction as either customer-initiated(CIT) or merchant-initiated(MIT). The customer-initiated transaction must contain the CVV in order for issuers to approve the transaction and providing the merchant with an issuer ID to use for future use. For every merchant-initiated transaction, the merchant must provide the issuer ID which was provided back by the issuer when the CIT transaction occurred.

How can it benefit you?

While the credentials on file mandate was created to protect the customer’s data primarily, there are benefits to the merchants as well. By using the credential on file feature merchants increase their authorization rate and reduce chargebacks on recurring transactions.

Credit Card Masking

July 15, 2020

What is the masking feature?

Masking feature allows the iFrame to mask the credit card and the CVV once the client has entered them. The masking feature is initiated through a parameter in the iFrame SRC URL. The middle 6 digits of the credit card number are masked along with the whole CVV for security reasons.

How can it benefit you?

The benefit of masking feature is that it ensures the credit card credentials are hidden for security reasons.

Additional Resources:

Data Residency

July 01, 2020

 What is Data Residency?

HostedPCI currently has Data Centers in four different regions around the world. Our current Data Centers are located in the USA, Canada, Belgium, and Australia. Many regions around the world have regulations regarding where the corporation data is stored. With the help of these four different data centers, merchants can select where their data should be stored based on their needs.

How can it benefit you?

The benefit of Data Residency is that it offers merchants a choice of where to store their corporate data. Using data centers in their region the merchants can ensure they have met the government regulations as well as serve their client better.

Auto Fill / Populate

June 01, 2020

What is Auto-FIll?

Autofill feature will easily populate the credit card credentials onto the payment form with which are stored within the browser. To initiate the auto-fill feature the field names and id have to be in a certain naming convention so the browser can identify those. The autofill feature will require the client to enter the CVV to ensure it is not a fraud transaction.

How can it benefit you?

The benefit of the auto-fill feature is it makes it quicker to fill out the credit card form and it makes the process smoother.

Additional Resources:

Gateway Tokenization

June 01, 2020

What is Gateway Tokenization?

HostedPCI now supports the ability for merchants to create gateway tokens with the gateway of their choice when they create a HostedPCI token. A gateway token can be created in 1 of 2 ways through HostedPCI. The first is by sending an API request to the gateway, this method provides the gateway token directly to the merchant, which they can use to make payments directly through to the payment gateway. The second method is for HostedPCI to create the token and store it on your behalf their for the merchant can continue to rely on 1 independent token while HostedPCI manages the additional tokens along with the real credit card.

How can it benefit you?

The benefit to being able to have multiple gateway tokens stored all with the HostedPCI token is that if at a later date you would like to switch payment gateway while being able to maintain credentials on the file you can because an initial transaction was already made with another payment gateway at the same time the credit card was taken from the client.

Early Tokenization

Januarary 05, 2020

What is Early Tokenization?

Early Tokenization is an HostedPCI iFrame feature that provides the HostedPCI token for the credit card as soon as the client has entered the credit card credentials. The Token is generated and returned before the client submits the payment form. The ‘normal’ tokenization occurs once the client clicks submit on the payment form but with early tokenization, the tokenization process occurs when the client is still filling out the rest of the payment form.

How can it benefit you?

The benefit of early tokenization is that it ensures fewer actions need to take place once the user submits the form. With early tokenization, once the form is submitted it will initiate the payment API directly. Otherwise, the full process including tokenization and initiating the payment API would occur once the form is submitted which can increase the chance for the process to run into any errors.

Additional Resources: