Payment integration types

Learn about the payment integrations provided by emerchantpay.

Choose from three types of emerchantpay payment integrations: Custom UI, Pre-built UI, and No-code. Select the right integration to best fit your specific business model and online architecture.

Custom UI

Implement your own UI through a direct server-to-server integration with the emerchantpay gateway for the most flexible integration. Use the emerchantpay API and SDK repositories in a variety of languages for full control over your online storefront, payment form, checkout process, and backend transaction requests.

As you will store and process customer data, you must meet the highest level of PCI DSS compliance : SAQ D. For each server-to-server integration, emerchantpay recommends you use the client-side encryption, a free library that encrypts customer data in their browser and reduces your PCI compliance requirement.

Pre-built UI

The Web Payment Form (WPF) is a hosted payment page hosted by emerchantpay, where your customer enters in their payment information at checkout. The WPF processes payments through all emerchantpay payment methods that are enabled for your account.

You can customise the WPF with a custom logo or colours, and can also display it in an iFrame on your own checkout page.

Because the WPF is hosted on emerchantpay’s servers, the secure processing of your customer’s payment information is handled by emerchantpay. This results in the lowest requirement for PCI DSS compliance: SAQ A.

No-code integrations

Use the emerchantpay Virtual terminal to process payments without an active storefront. Because the virtual terminal is enabled through your Genesis merchant console, it does not require you to code or host a payment page and is ideal for accepting payments while you build your storefront or if your servers are down for maintenance.

Send payment links with Pay by link that use the WPF configured for your Merchant account to gather your customer’s payment information. Customise the appearance of payment links just as you would the WPF.

Process MOTO payments with the Lightweight Virtual Terminal, a limited-access virtual terminal that you provide to your employees. Also available on a mobile device, the Lightweight Virtual terminal is the equivalent of a POS terminal to process in-person payments.

Compare integration types

Server-to-server Server-to-server with Client-side encryption Web Payment Form (WPF) Virtual terminal
Coding Complex Complex Simple None
API integration Processing API Processing API WPF API None
Supported payment methods All All All* All
UI/UX configurability Full Full Partial Partial