> For the complete documentation index, see [llms.txt](https://developer.magtek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.magtek.com/services/magensa/mppg-unigate.md).
# MPPG/Unigate
This page is your entry point for integrating with **MPPG/Unigate**, Magensa's API for omni-commerce payment processing across both card-present and card-not-present channels. Use the **Unigate API** reference below to explore transaction types, credentials, and processor responses in an interactive Postman collection, or open a **web-based demo** to watch the full flow in action — from a MagTek reader, through the browser, to the gateway and back — with or without physical hardware.
### **Unigate API**
| **API Section** | **Description** |
| ---------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**Intended Audience**](https://unigate.developer.magtek.com/#intended-audience) | Who this documentation is for, and what to have ready — written for hands-on developers comfortable with REST APIs, with a Postman account for running the sample requests. |
| [**Overview**](https://unigate.developer.magtek.com/#overview) | What Unigate is and how it works — a single, unified API that normalizes requests and responses across multiple processors and hardware, covering card, Apple Pay, and Google Pay payments via MPPG V5 or later. |
| [**Quickstart guide**](https://unigate.developer.magtek.com/#quickstart-guide) | Get running quickly: copy the Postman collection, format your Pilot credentials as Basic Auth, and send your first EMV Sale or Authorize against your test account. |
| [**Processor Responses**](https://unigate.developer.magtek.com/#processor-responses) | Sample responses from each supported processor (Fiserv, TSYS, Worldpay, Heartland, EPX, Chase, Elavon), showing how status, date, and amount formats differ between them. |
| **Normalized Processor Response Fields** | A standardized response structure (added March 2025) that maps processor-specific fields to common keys, so you can consume results consistently without per-processor parsing. |
| ***Transaction*** | Initial financial requests to a processor (for example, Sale or Authorize), organized by entry method and payment type. |
| [**EMV**](https://unigate.developer.magtek.com/#d7dba37e-654b-4ee0-9d80-01e1e76c33e3) | Process a chip-card transaction (contact or contactless) using the EMV ARQC cryptogram read from a MagTek device. |
| [**Token**](https://unigate.developer.magtek.com/#8964a596-f957-4db0-bca7-b6a6c7dd7204) | Charge a stored token — issued by the Tokenization service or returned from a prior transaction — in place of raw card data. |
| [**CardSwipe**](https://unigate.developer.magtek.com/#8aaddbb2-9a8a-4bcd-9413-eb1036736056) | Process a magnetic-stripe transaction from encrypted swipe data captured by a MagTek reader. |
| [**KeyPadEntry**](https://unigate.developer.magtek.com/#2f8ad189-bda2-4dba-bbf6-62306bf473ec) | Process a transaction from card data entered on the device's secure keypad. |
| [**ManualEntry**](https://unigate.developer.magtek.com/#26a0d517-2dd8-487b-9c19-7c04adc7db48) | Process a card-not-present transaction from card data keyed into your application. |
| [**InAppApplePay**](https://unigate.developer.magtek.com/#ad08c651-d101-4ce5-a377-853f0fdd7f96) | Accept Apple Pay inside a native mobile app using the app's Apple Pay payment token. |
| [**TECApplePay**](https://unigate.developer.magtek.com/#a6b1ac43-36cd-4528-ad25-63a78f97ee13) | Accept Apple Pay on the web through Magensa TokenExchange Connect (TEC) for eCommerce checkout. |
| [**GooglePay**](https://unigate.developer.magtek.com/#64975536-ff3d-45d1-b6e0-45a86e75a47e) | Accept Google Pay using the wallet's encrypted payment token. |
| ***Reference Transaction*** | Follow-up actions against an existing transaction (for example, Capture, Refund, or Void), referenced by a prior transaction rather than new card data. |
| [**Incremental Authorization**](https://unigate.developer.magtek.com/#3f0cf11a-0abc-430c-ad99-c9a6c349220d) | Raise the approved amount on an existing authorization — common for bar tabs, hospitality, and other open checks. |
| [**Tip Adjust**](https://unigate.developer.magtek.com/#8345b7e6-40a4-4393-bd32-8c2b3d8747a2) | Add or change a gratuity on a previously authorized transaction before it settles. |
| [**Capture**](https://unigate.developer.magtek.com/#f47ef3e3-19ba-4835-b0b8-70cd6201380d) | Settle a previously authorized transaction to collect the approved amount. |
| [**Refund**](https://unigate.developer.magtek.com/#a94c5bda-f0cf-4c58-8bb4-fe3766f3c21a) | Return funds to the cardholder for a prior transaction. |
| [**Void**](https://unigate.developer.magtek.com/#0239d807-c594-4aae-b3b6-f7b30bce66b3) | Cancel a transaction before it settles, releasing the authorization hold. |
| [**Recall Transaction**](https://unigate.developer.magtek.com/#9becfa1a-adca-40b8-96dc-acc7c82d0f94) | Retrieve the details and status of a prior transaction by reference. |
| [**Slingshot (Disgout/PAX Users Only)**](https://unigate.developer.magtek.com/#88d8b048-33b9-4eaa-9320-d3e82dc1ce3c) | High-performance data-transfer service for DishOut and PAX terminal integrations. |
| [**AppleTapToPay Token**](https://unigate.developer.magtek.com/#5bcf00b0-0b07-4b3d-b7e8-a9b33ad49932) | Accept contactless payments with Tap to Pay on iPhone (MPoC) — the iPhone acts as the reader, with no separate hardware. |
### **Web-based Demos**
| **Web Demo** | **Description** |
| ------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------- |
| [**MMS Unigate Demo**](https://rms.magensa.net/Test/demo/mmsUnigateDemo.html) | This demonstrates how to perform an EMV Sale transaction with a MagTek card reader and MPPG/Unigate. |
| [**MMS Unigate Vending Demo**](https://rms.magensa.net/Test/demo/mmsUnigateVend.html) | This demonstrates how to perform a simulated vending transaction for an EMV Sale using a MagTek card reader and MPPG/Unigate. |
| [**Unigate Demo**](https://rms.magensa.net/Test/demo/UnigateDemo.html) | This demonstrates the flow of a wide array of transaction types using MPPG/Unigate. |
| [**MMS Unigate Local Start**](https://rms.magensa.net/Test/demo/mmsUnigateLocalStart.html) | This demonstrates how DynaFlex II PED can be used to initiate a Sale transaction using its touchscreen prompts and MPPG/Unigate. |
| [**Disclaimer**](https://rms.magensa.net/Test/demo/Disclaimer.html) | Legal notifications |
### Need More Help
{% hint style="info" %}
**Need Help?**
For additional support, please contact MagTek Support:
**Technical Support:**
* 📧 **Email:** [support@magtek.com](mailto:support@magtek.com?subject=Support%20Request)
* 📞 **Phone:** 1-562-546-6800 (US)
* 🕐 **Hours:** Monday-Friday, 5:30 AM - 5:00 PM PST
**Online Resources:**
* 🌐 **Support Portal:** developer.magtek.com
**Documentation Feedback:**
Help us improve this documentation! [feedback@magtek.com](mailto:feedback@magtek.com?subject=Feedback)
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://developer.magtek.com/services/magensa/mppg-unigate.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.