Version 1.0
A fully hosted payment page offers a simple, customizable payment solution with low levels of PCI requirement overheads by keeping sensitive cardholder data out of your systems and requires minimal integration effort.
You can use the Hosted Payment Page in two ways:
- On its own to process payments when you collect card details on your site.
- To create multiple payment experiences by configuring separate profiles for different business needs.
Key Steps for Integration
- Review the Key Features and Benefits and Integration Feature Comparison sections to learn more about the hosted payment pages and their capabilities. Consider this information before you start your integration. Make sure that a this integration is the best choice for your system. One of our other integration methods might work just as well, and require less effort to integrate in to your system.
- Access the Smartpay Fuse portal to create a Hosted Checkout profile.
- Configure account settings to define the functionality, appearance, and branding of your payment page.
- Test your integration thoroughly.
Fully Hosted Payment Pages provide these key benefits:
- Low integration overhead
- Minimal PCI overhead
- Accepts a wide range of card types such as American Express, Mastercard, and Visa
- Payment page customization
- Simple redirection of the customer browser
- 3D Secure ready
Secure Acceptance Hosted Payment page is one of several methods to accept payments on your site. Smartpay Fuse offers additional methods that provide different features. Before you start your integration, make sure you choose the right method for your needs. If the capability you need is not supported with Secure Acceptance Hosted Checkout solution, consider using one of the alternate integration methods.
For more information about these integration options, refer to these quick start guides:
- E-commerce Plugins: provides an easy integration for supported e-commerce platforms.
- Virtual Terminal: no integration is required because servicing agents take payments using our back-office portal, Smartpay Fuse Portal.
- Hosted Fields: you can capture individual payment card details as PCI-safe fields.
- REST API: full, back end integration using our REST API.
Contact us if you have questions about Secure Acceptance Hosted Payment Pages.
This table provides a comparison of the features that are available in the different integration methods.
Integration Methods | |||||
---|---|---|---|---|---|
Features | Virtual Terminal 1 | E-Commerce Plugins | Hosted Payment Page | Direct REST API | Hosted Fields |
PCI overhead | SAQ C-VT | Mixed2 | SAQ A | SAQ D | SAQ A3 |
Transaction Types | |||||
Authorization only |
Yes | Yes (all) | Yes | Yes | Yes7 |
Authorization and capture |
Yes | Yes (all) | Yes | Yes | Yes7 |
Tokenise card (COF) |
Yes | Yes | Yes4 | Yes | Yes7 |
CIT (initial/subsequent) |
Yes | Yes | Yes4 | Yes | Yes7 |
MIT (continuous authority) |
No | Some6 | No | Yes | Yes7 |
Refund (standalone) |
Yes8 | Some6 | REST API & Smartpay Fuse Portal1 | Yes | Yes7 |
Refund (existing transaction) |
Yes | Yes (all) | REST API & Smartpay Fuse Portal1 | Yes | Yes7 |
Reversal |
Yes | Yes (all) | REST API & Smartpay Fuse Portal1 | Yes | Yes7 |
Capture of standalone authorization |
No | Yes (all) | REST API & Smartpay Fuse Portal1 | Yes | Yes7 |
3-D Secure (v2) | N/A | Yes (all) | Yes | Yes | Yes7 |
Account validation | N/A | Some6 | Yes | Yes | Yes7 |
Basic fraud rules5 | Yes | Yes (all) | Yes | Yes | Yes7 |
Low value exemptions | N/A | No | Yes | Yes | Yes7 |
AVS/CSC Auto Reversal/Blocking | Yes8 | Yes6, 8 | Yes8 | Yes8 | Yes7, 8 |
Digital Wallets | |||||
Apple Pay |
N/A | Some6 | No | Yes | No7 |
Google Pay |
N/A | Some6 | No | Yes | No7 |
Card Types | |||||
Visa |
Yes | Yes | Yes | Yes | Yes |
Mastercard |
Yes | Yes | Yes | Yes | Yes |
American Express |
Yes8 | Yes8 | Yes8 | Yes8 | Yes8 |
Channels | |||||
E-Commerce |
No | Yes | Yes | Yes | Yes7 |
Moto |
Yes | Some6 | Yes8 | Yes | Yes7 |
Notes:
1: The Smartpay Fuse Portal is our back-office servicing portal.
2: Different plugins use different integration methods. Refer to the applicable quick start guide listed and linked above for details about the PCI implications of those integration methods. Contact support if you have concerns or questions about PCI implications.
3: SAQ A applies when Flex Microforms is used to tokenize from web applications.
4: Secure Acceptance Hosted Checkout creates tokens from initial CIT transactions that can be used for subsequent CIT transactions.
5: Basic velocity rules using Decision Manager are only available for SME clients. Advanced fraud check and TRA are handled on a case-by-case basis.
6: These features are only available on some of our plugins (refer to the individual plugin solution pages for more information).
7: Flex Microform allows card numbers to be safely tokenized in compliance with PC standards. The resulting transient token is used to process or manage the transaction using the direct integration REST API.
8: These features are not enabled out of the box and need further configuration by our support team.
The figure below shows the stages of the payment flow using Fully Hosted Payment Pages.
- The customer processes their order on the merchant website.
- The customer's system requests a payment form.
- Smartpay Fuse creates a payment form and sends it to the customer.
- The customer's system displays the payment form.
- The customer enters their card details.
- The customer computer sends card details to Smartpay Advance.
- Smartpay Fuse receives the card information and processes the transaction.

This integration option provides a PCI SAQ A level of compliance when used to host payment form frames within a web page.
Card details are entered on a customer browser and are sent directly to Smartpay Fuse. When the form is submitted, payment data is submitted directly to Smatpay Fuse and never touches your systems.
If you have any questions or concerns about the PCI implications of using Fully Hosted Payment Pages, contact us.