Charge To Account Gateway Technical Information (Including MX Pay)

Overview

The MX Telecom Charge To Account Gateway enables you to charge individual end users for one-off purchases and subscription services using the MX Pay WAP billing solution. A subscription's charges and lifecycle can be managed entirely by the gateway.

Each US carrier provides a different system for charging end users. The Charge To Account Gateway offers a common API enabling your application to charge end users of different carriers, reducing the time spent on integration.

AT&T, T-Mobile and Virgin Mobile are currently supported in the US, with support for more carriers coming soon.

Features

• Integration with your application using HTTP requests
• Plain text or XML response format
• Support for one-off charges or recurring charges as part of a subscription

Requirements

• You must be able to send standard HTTPS GET/POST requests
• You must host a URL to receive incoming HTTP notifications from the Charge To Account Gateway

One-off Charges

How to process one-time payments using the Charge To Account Gateway.

Single Click

Offering Payforit Single Click transactions via the Charge To Account Gateway.

Subscriptions

How to charge for subscription services using the Charge To Account Gateway.

Status Codes

How to interpret the status codes sent by the Charge To Account Gateway.

Branding

How to customise the merchant information that is displayed on Payforit confirmation pages; how to use the Charge To Account Gateway's support for multiple brands.

Marketing Opt-ins

How to collect marketing opt-ins through Payforit using the Charge To Account Gateway.

Anonymous User ID

How to use the Charge To Account Gateway to identify visitors to your WAP/XHTML site and retrieve information about them without knowing their mobile numbers.

Carrier Features

Available features of the Charge To Account Gateway API vary slightly between carriers; this page gives a comparison.