Developer Resources for Payment Integrations

As a software company that provides payment processing services, Host Merchant Services has an added advantage when supporting partner integrations, because the same developers build our Cloud Manager products. This page covers what your development team gets: access, environments and support.
Request Developer Access
Two software developers collaborating at a computer workstation to build and test payment processing integrations.

Private API Access

Sandbox and UAT Environments

Developer Support

OR

We Perform the Integration for You

What You Get

We provide private API access, sandbox and UAT environments, and developer support to build the integration. Alternatively, we can perform the integration for you.

Documentation and support are scoped to the integration path you select, so your team receives the material for that path rather than a general document set. All paths run on PaymentCore, the HMS PayAPI.

Integration Paths

Choose the connection that fits your product. Each path below is available today, and we provide the documentation for the one you select.

HMS PayAPI (PaymentCore)

Direct integration with our payment layer for teams that want complete control of the payment experience within their software.

PaymentCore

Hosted Payment Page

The quickest way to get payments live, with no card data passing through your systems.

Embedded Fields

HMS-hosted payment fields delivered through an iframe and embedded in your software, so you keep your look and feel while HMS handles the card data.

Pay Links and Invoices

Collect payments without building a payment interface in your software.

Semi-Integrated Terminals

Your software drives Dejavoo, Clover, PAX and Valor terminals for in-person payments.

Existing Gateway Integrations

Bring a connection to NMI, Authorize.Net, TSYS TransIT, CardPointe or FluidPay into the integration.

Direct Processor Certification

HMS supports certification with TSYS or CardConnect for teams that want to process directly.

Environments and Access

There is a development environment for writing code, and a UAT environment for acceptance testing. Nothing reaches the production environment until testing is complete.
Documentation is shared with partners once the integration path is agreed, and it covers that path in full, not just API keys or test credentials.
Request access below if your team needs API documentation, test credentials or sample code.

Step 1

Sandbox

Step 2

UAT Environment

Step 3

Production Environment

Certification and PCI

PaymentCore has already gone through the certification process with TSYS and CardConnect and others. Using PaymentCore’s processing means your software doesn’t need to go through certification itself. We configure our integrations to keep card data out of your systems to keep PCI scope as small as possible. If your product needs to go through TSYS or CardConnect’s certification process, HMS can assist with that as well. The differences between the two routes are covered in the SaaS Partner FAQ.

Digital security shield displayed above a laptop representing PCI compliance, data protection, and secure payment processing integrations.

Support

Development Integration Support

Support starts with development integration support, where your developers build against our sandbox with our engineers assisting.

White-Glove Integration

It also includes white-glove integration, where HMS builds the integration for you.

  • You choose the option when the partnership is defined.

Request Access

Give us the details on your company, your product, your integration plans, and your timeframe. We’ll get back to you with next steps and, once the integration path is defined, access to the documentation for it.
Request Developer Access

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Name*
For the commercial side of the partnership, see the SaaS & ISV Partner Program. For the gateway itself, see HMS Pay.
Technical support representatives wearing headsets and working at computers to assist developers with payment API integrations.

Frequently Asked Questions

Is the API documentation public?
No. Documentation is made available privately once we agree on an integration path. Your team is provided the documentation, as well as sandbox and UAT environments and developer support. To gain access, fill in the form on this page.
Yes. A sandbox and a UAT environment are made available for your team to test the integration. Documentation for integration paths is made available to team members to facilitate the testing and integration process.
Yes. HMS can build the integration and provide merchant support once it is built. Alternatively, your developers build the integration in the sandbox with support from HMS developers. The same developers build HMS’s Cloud Manager.
TSYS and CardConnect, as well as Dejavoo, Valor and others.