MercuryActivate Overview

Document created by chadb on May 10, 2016Last modified by Chris Jennings on Mar 9, 2017
Version 6Show Document
  • View in full screen mode

MercuryActivate is an enrollment service that enables merchants to apply to Vantiv Integrated Payments on the MercuryPay processing platform, through an online form. This shortens the enrollment time so that your merchants can start processing payments as quickly as possible. MercuryActivate offers especially fast turn-around times for enrollment types where details such as contract pricing have been pre-negotiated.


All personally identifiable information (PII), is encrypted on the backend, and is never returned, either in the responses or status queries. Only provisioned developer APIs have the ability to connect to our endpoint, and the connection is by request through encrypted SSL.


The MercuryActivate service is designed to be flexible so you can tailor the data collected to match your own sales process. It uses a simple web service that is integrated into your system. This may be implemented as either a hosted web site for merchant enrollment, as part of your POS software suite, or integrated into SalesForce. In all cases the enrollments are routed through your site to Vantiv Integrated Payments, LLC. This simplifies the integration with Vantiv IP’s enrollment service and shortens your development time.


Get a test API Key and password from Mercury

An API Key is required for a developer to communicate with the MercuryActivate service.  Each API Key is unique for that developer. It is also unique to the certification service used for testing. To obtain a certification API Key, contact


Build your RESTful format: JSON or XML

The RESTful API can pass messages that are either JSON-formatted or XML-formatted; the entry points are identical.

The message formatting is determined by the HTML headers passed to the service.  If you omit specific instructions for what type of message format you are using, the service will default to XML.


  • With the XML style, the data elements must be maintained in the same order as listed in the documentation. Out of order elements will cause missed values.
  • The JSON format is not picky about element order.


Using JSON


JSON formatted requests and responses are used over HTTPS for transaction processing.



The base endpoint address for the RESTful MercuryActivate Service is



Authentication occurs via HTTP Basic Auth using an HTTP authorization header.

Username: existing MerchantID

Password: created and stored by Mercury

  1. Create string of [username]:[password]
  2. BASE64 encoded string
  3. Set Authorization header value to: “Basic [encoded string]”



Set Content-Type header value to: “application/json”


Submission and Status Addresses

All test transactions are posted to





Developer  ServerAddress


To submit an application through an HTTP POST


To get the statusof the application via an HTTP GET{id}

Where {id}is the integer representing the application ID returned from the submission.



JSON example for a an application submission

  "OwnerTitle":"General Manager Store 5150", 
  "OwnerAddress":"200 Main St", 
  "DBAName":"What’s For Dinner?", 
  "DBAAddress":"100 Main St", 
  "LegalName":"Zoom Dinner Inc", 
  "LegalAddress":"300 Main St", 
  "ProductServiceSold":"Prepared Food", 
  "Dda":"123 4567 8900", 


Status Response Message

  "ApplicationId": "0D9217A9-1559-437D-A1A6-6283215CAD44"



View Next: MercuryActivate Integration Guide