Integrations

We offer a variety of solutions to meet your needs. Bank of America's Healthcare Omni-Channel Gateway is an enterprise-grade payment platform with a proprietary, certified PCI-validated P2PE gateway. With cloud-based device management, including remote key injection and device encryption, merchant acquiring, and centralized reporting capabilities, our Healthcare Omni-Channel Gateway addresses the end-to-end payments needs of hospitals and enterprise health systems.

Our API and our cloud-based service makes it easy to include payment services. Your software can create transactions without storing, sending or processing credit card data, saving time and the cost of PCI Compliance!

Security

What is the Security Solution?

  1. SSL/TLS encapsulation of communication
  2. PCI validated P2PE solution
  3. Reduce Cardholder Data Environment scope
  4. Terminal to Gateway P2PE communication
  5. Certified key injection facility

What is in-Scope of the EMV and PCI DSS Bubble?

  1. Segmentation of the cardholder data environment (CDE)
  2. No direct communication of sensitive data through the PC or application

This diagram shows secure payment processing via partner software and hardware, Transaction Broker API, and Healthcare Omni-Channel Gateway. Healthcare Omni-Channel Gateway is SSL/TLS encapsulation of communication, PCI validated P2PE solution, Terminal to Gateway P2PE communication, Certified Injection facility, Reduced Cardholder Data Environment scope. Healthcare Omni-Channel Gateway API's provide Terminal communication, Easy RESTful API, Reporting tool. Control Center allows for Multi-Merchant mapping, Terminal management, Automatic Terminal management. IngEstate allows Remote terminal communication, Terminal software repository, Diagnostic log software.

What is Healthcare Omni-Channel Gateway

APIs

  • Terminal communication
  • Easy RESTful API
  • Reporting tool

Control Center

  • Multi-Merchant mapping
  • Terminal management
  • Automatic terminal updating

IngEstate

  • Remote terminal communication
  • Terminal software repository
  • Diagnostic log software

This diagram shows secure payment processing via partner software and hardware, Transaction Broker API, and Healthcare Omni-Channel Gateway. Healthcare Omni-Channel Gateway is SSL/TLS encapsulation of communication, PCI validated P2PE solution, Terminal to Gateway P2PE communication, Certified Injection facility, Reduced Cardholder Data Environment scope. Healthcare Omni-Channel Gateway API's provide Terminal communication, Easy RESTful API, Reporting tool. Control Center allows for Multi-Merchant mapping, Terminal management, Automatic Terminal management. IngEstate allows Remote terminal communication, Terminal software repository, Diagnostic log software.

EMV Supported Processors

  • TSYS
  • Fiserv
  • Elavon
  • WorldPay
  • HeartLand
  • Global Payment
  • Vantiv

This diagram shows secure payment processing via partner software and hardware, Transaction Broker API, and Healthcare Omni-Channel Gateway. Multiple EMV supported processors are TYSY, Fiserv, Elavon, WorldPay, HeartLand, Global Payment, Vantiv. When Transaction is Initiated a request is sent to Healthcare Omni-Channel Gateway, Healthcare Omni-Channel Gateway initiates terminal application, Terminal accepts card data and sends to Gateway, Gateway communicates with processor, Gateway returns response to terminal, Terminal returns response to Healthcare Omni-Channel Gateway. Healthcare Omni-Channel Gateway sends results via Callback URL. Healthcare Omni-Channel Gateway returns in pool response.

Callback URL

Transaction Initiation

  1. Transaction request sent to Healthcare Omni-Channel Gateway
  2. Healthcare Omni-Channel Gateway initiates terminal application
  3. Terminal accepts card data and sends to Gateway
  4. Gateway communications with Processor
  5. Gateway returns response to terminal
  6. Terminal returns response to Healthcare Omni-Channel Gateway

Result Status

  1. Healthcare Omni-Channel Gateway sends results via Callback URL

This diagram shows secure payment processing via partner software and hardware, Transaction Broker API, and Healthcare Omni-Channel Gateway. Multiple EMV supported processors are TYSY, Fiserv, Elavon, WorldPay, HeartLand, Global Payment, Vantiv. When Transaction is Initiated a request is sent to Healthcare Omni-Channel Gateway, Healthcare Omni-Channel Gateway initiates terminal application, Terminal accepts card data and sends to Gateway, Gateway communicates with processor, Gateway returns response to terminal, Terminal returns response to Healthcare Omni-Channel Gateway. Healthcare Omni-Channel Gateway sends results via Callback URL. Healthcare Omni-Channel Gateway returns in pool response.

Polling

Transaction Initiation

  1. Transaction request sent to Healthcare Omni-Channel Gateway
  2. Healthcare Omni-Channel Gateway initiates terminal application
  3. Terminal accepts card data and sends to Gateway
  4. Gateway communications with Processor
  5. Gateway returns response to terminal
  6. Terminal returns response to Healthcare Omni-Channel Gateway

Result Status

  1. Healthcare Omni-Channel Gateway sends results via Callback URL
  2. Healthcare Omni-Channel Gateway returns result in poll response

This diagram shows secure payment processing via partner software and hardware, Transaction Broker API, and Healthcare Omni-Channel Gateway. Multiple EMV supported processors are TYSY, Fiserv, Elavon, WorldPay, HeartLand, Global Payment, Vantiv. When Transaction is Initiated a request is sent to Healthcare Omni-Channel Gateway, Healthcare Omni-Channel Gateway initiates terminal application, Terminal accepts card data and sends to Gateway, Gateway communicates with processor, Gateway returns response to terminal, Terminal returns response to Healthcare Omni-Channel Gateway. Healthcare Omni-Channel Gateway sends results via Callback URL. Healthcare Omni-Channel Gateway returns in pool response.

Tokenization

Transaction Initiation

  1. Transaction request sent to Healthcare Omni-Channel Gateway
  2. Healthcare Omni-Channel Gateway initiates terminal application
  3. Terminal accepts card data and sends to Gateway
  4. Gateway stores card data and sends to Gateway
  5. Gateway returns response to terminal
  6. Terminal returns response to Healthcare Omni-Channel Gateway

Result Status

  1. Healthcare Omni-Channel Gateway is polled for result
  2. Healthcare Omni-Channel Gateway returns result in poll response

This diagram shows secure payment processing via partner software and hardware, Transaction Broker API, and Healthcare Omni-Channel Gateway. Multiple EMV supported processors are TYSY, Fiserv, Elavon, WorldPay, HeartLand, Global Payment, Vantiv. When Transaction is Initiated a request is sent to Healthcare Omni-Channel Gateway, Healthcare Omni-Channel Gateway initiates terminal application, Terminal accepts card data and sends to Gateway, Gateway communicates with processor, Gateway returns response to terminal, Terminal returns response to Healthcare Omni-Channel Gateway. Healthcare Omni-Channel Gateway sends results via Callback URL. Healthcare Omni-Channel Gateway returns in pool response.

Terminal Prompt

Tokenization Initiation

  1. Prompt request sent to Healthcare Omni-Channel Gateway
  2. Healthcare Omni-Channel Gateway initiates Terminal
  3. Terminal accepts input and sends to Healthcare Omni-Channel Gateway

Result Status

  1. Healthcare Omni-Channel Gateway is polled for result
  2. Healthcare Omni-Channel Gateway returns in poll response

This diagram shows secure payment processing via partner software and hardware, Transaction Broker API, and Healthcare Omni-Channel Gateway. Multiple EMV supported processors are TYSY, Fiserv, Elavon, WorldPay, HeartLand, Global Payment, Vantiv. When Transaction is Initiated a request is sent to Healthcare Omni-Channel Gateway, Healthcare Omni-Channel Gateway initiates terminal application, Terminal accepts card data and sends to Gateway, Gateway communicates with processor, Gateway returns response to terminal, Terminal returns response to Healthcare Omni-Channel Gateway. Healthcare Omni-Channel Gateway sends results via Callback URL. Healthcare Omni-Channel Gateway returns in pool response.

Our Getting Started Guides will help you along in your upcoming integration. Please take a look at them as you are planning out your integration.

Getting Started Guides

Integration Resources

Upgrade to Healthcare Omni-Channel Gateway 2.0

Starting your Integration

The postman collection and environment are available to you to download for a quick start to see how the restAPI calls will work. The set up of these files are very simple, however we do supply you with instructions on how to set them up.

Postman Learning Center

Setup Instructions

Collection

Environment

Postman Hints

Once the collection and environment has been imported and configured Postman can show you examples of the restAPI call you are looking to use in many different languages.

Each integration will have to be certified by one of our Integration Specialist before an integration launch. These documents are available for to review and show what we will be looking for in a certification test. Not all of these documents will apply to each integration that is being built and are displayed in the order of the most commonly used Test Cases.

Test Case Scenarios

Hosted Payment Page

Terminal Test Case

Non Terminal Test Case

IVR Test Case

Reporting Test Case

Settings Test Case

Prompt Jobs Test Case

Pre-Authorization Test Case

Google Pay™ - Integration Guide

Why Google Pay

Google Pay is a fast and secured method making payments on websites and terminals.

Start accepting Google Pay payments in your HPP page and terminals, it will allow your customers to make payments in a few clicks. By adding Google Pay you are simplifying the payment process for your customers.

More information in "About Google Pay"

Google Pay Benefits

  • Convenience - Paying with Google Pay is easy and comfort, the payment doesn't involve any payment card directly, and can be completed in few clicks, all the payment information is stored inside the mobile wallet or in Google cloud and sent with the payment.

  • Simplicity - By adding Google Pay as a payment you are drastically increase the probability of a payment being made.

  • Security - Google Pay is a secured way to submit and process payments. Google Pay is utilizing security mechanisms and processes on multiple levels and protecting customers payment data and private information.

  • Modern - Google Pay is a modern and technologically advanced way to make payments, in general today customers are seeking a way to make payments in a secure and fast manner and Google Pay is helping them.

  • Global - Google Pay is supported all over the world. You can accept payments from any place on the planet.

How It Works

Adding card to mobile wallet - flow

Diagram of Google Pay service to complete online transactions via Google Wallet on supported devices.

This workflow shows how you can add card to wallet. When the card holder adds the card the issuer replaces the original card number with a DPAN token and the DPAN token is stored in the mobile wallet and used for making payments. This way the original card number (FPAN) is never disclosed which makes the payment process very secure. To make a payment with DPAN the mobile wallet app, also produces a cryptogram and the payment is made with a combination of DPAN and the cryptogram, so even if the DPAN was disclosed, it can't be used without the cryptogram and the cryptogram is regenerated every time payment is made.

Mobile wallet payment processing - flow

Diagram of Google Pay service to complete online transactions via Google Wallet on supported devices.

This workflow shows how mobile wallet processing happens. When a payment is submitted using google pay an encrypted google pay token is created. The token content has Billing Address (if requested), Shipping Address (if requested), Email (if requested), Phone Number (if requested), DPAN token number, Cryptogram. Healthcare Omni-Channel Gateway will decrypt token, validate token and process the payment providing a Payment result (approved or declined).

Google Pay Compatibility

Supported Browsers

Supported Card Networks

  • VISA

  • Master Card

  • American Express

  • Discover

Supported Card Authorization Methods

  • Credit

  • Debit

Supported Google Pay Authentication Methods

  • 3DS (CRYPTOGRAM_3DS) - This authentication method is associated with cards stored as Android device tokens. Returned payment data includes a 3-D Secure (3DS) cryptogram generated on the device.

  • FPAN (PAN_ONLY) - This authentication method is associated with payment cards stored on file with the user's Google Account. Returned payment data includes personal account number (PAN) with the expiration month and the expiration year.

Add Google Pay to Hosted Payment Page

Checklist

  • All merchants must adhere to the Google Pay APIs Acceptable Use Policy and accept the terms defined in the Google Pay API Terms of Service

  • If you don't have a Google Pay merchant id, please sign up for Google Pay business account

  • Please read the Google Pay Web developer documentation, Google Pay Web integration checklist and the Google Pay Web brand guidelines

  • Prepare the hosted payment page template htmlHosted Payment Page

  • Add the following meta tag element to the template header section:

  • Add the following two script files to the template header section:

  • Add a <div> element to the template, with the name="google-pay-button", in place where you want to display the Google Pay button

  • You can also add the following attributes to the payment button element in order to customize it's appearance

    • button-color: 'default', 'black', 'white'

    • button-type: 'plain', 'long', 'short'

    • button-size-mode: 'static', 'fill'

  • Ensure Google Pay button uses all approved branding - Brand Guidelinesfor Google Pay Button

  • Upload the template by using Hosted Payment Page template management console.

  • Add the attribute "allowpaymentrequest" to the iframe element hosting the payment hosted page

  • Contact Healthcare Omni-Channel Gateway integration support with the following information:

  • Your Google Pay Merchant Id (The Merchant Id is located in the right top corner of you Google Pay business console) - more infoabout Google Pay Business Console

  • Card authentication methods you want to support (more informationabout Card Authentication Methods).

  • CRYPTOGRAM_3DS - Is used only on Android mobile phones from version: Lollipop (5.0) or higher) - if only this option is selected, the Google Pay will be enabled only for Android - Lollipop (5.0) or higher and only for cards, that were specifically tokenized on the used device.

  • PAN_ONLY - Is used for card stored in the Google account, this method is supported on all the devices (Windows, IOS, OSX, Android).

Confirm if billing contact information is required

  • Email

  • Phone number

Address - Google Pay supports two billing address formats (please specify the required format)

Full

  • Name

  • Street

  • City

  • State

  • Zip

Minimal

  • Name

  • Zip

  • After AxiaMed integration support, confirms that everything is set according to requirements, test if Google Pay is available on your hosted payment page and you can complete the payment.

Payment Page

Payment page description

Wallet

Wallet page description

Hosted Payment Page - Putting it's all together