# US 2012/0095905 A1 · Payment gateway for processing payment requests associated with a wireless users account

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0095905 A1
- Document ID: US20120095905A1
- Status: Published application
- Kind: A1
- Application number: 12/904,217
- Filed: 2010-10-14
- Published: 2012-04-19
- Earliest claimed: 2010-10-14
- Assignees: Syniverse Technologies, LLC
- Inventors: Richard Lance Hodges
- Web page: https://patentgrep.com/patent/US20120095905A1

## CPC

- G06Q 20/027: {involving a payment switch or gateway}
- G06Q 20/10: specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q 20/28: Pre-payment schemes, e.g. "pay before"
- G06Q 20/3221: {Access to banking information through M-devices}
- H04M 15/00: Arrangements for metering, time-control or time indication {; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP}
- H04M 15/06: Recording class or number of calling {, i.e. A-party} or called party {, i.e. B-party}
- H04M 15/43: {Billing software details}
- H04M 15/47: {Fraud detection or prevention means}
- H04M 15/48: {Secure or trusted billing, e.g. trusted elements or encryption}
- H04M 15/68: {Payment of value-added services}
- H04M 15/8038: {Roaming or handoff}
- H04W 4/24: Accounting or billing
- H04M 2215/2026: Wireless network, e.g. GSM, PCS, TACS
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A Payment Gateway interfaces, in one embodiment, with a merchant's website or a payment aggregator used by the merchant's website, for facilitating purchases made at the website by a wireless user. In one embodiment, purchases at the website are paid for by charging the wireless user's prepaid account maintained in the mobile operator. The Payment Gateway accepts messages in an HTTP based message from the website or payment aggregator and provides a gateway function to the wireless user's service provider, which is accessible only using SS7 based MAP protocols. The mobile gateway ascertains the proper message syntax to use in a MAP based USSD message based on the wireless carrier. The mobile gateway also receives messages from the mobile operator, typically using a GSM MAP based protocol and initiates HTTP based messages back to the merchant's website.

## Claims

### Claim 1

A gateway system for processing payment related requests associated with a wireless user comprising:
a processor configured to perform the steps of:
a) receive at a first interface from a source a first charge request message requesting a charge operation to an account associated with a wireless user, said first charge request message comprising a first HTTP formatted message comprising an identifier associated with said wireless user and a charge amount;
b) generate at a second interface to a mobile operator a first GSM based request message comprising a first Unstructured Supplementary Service Data (“USSD”) message requesting said charge operation and indicating said charge amount, said first GSM based request message comprising an international mobile subscriber identity (“IMSI”) associated with said wireless user;
c) receive at said second interface a first GSM based response message comprising a second USSD message received in response to said first GSM based request message, wherein said first GSM based response message confirms said charge to said account by said mobile operator; and
d) generate at said first interface a first charge response message to said source comprising a second HTTP formatted message confirming said charge to said account by said mobile operator.

### Claim 2 (depends on 1)

The system of claim 1 further comprising:
a memory, wherein said memory is configured to store a data string associated with said mobile operator of said wireless user, said data string defined as indicating said charge operation to said mobile operator, said memory providing said data string to said processor for incorporation into said first GSM based request message.

### Claim 3 (depends on 2)

The system of claim 2 wherein said processor is further configured to perform, prior to receiving said first charge request message, the step of:
receive at said first interface a second request message from said source comprising a third HTTP formatted message, wherein said second request message comprises a mobile telephone number of said wireless user.

### Claim 4 (depends on 3)

The system of claim 3 wherein said processor is further configured to perform the steps of:
a) generate at said second interface a first GSM based IMSI request message comprising said mobile telephone number to said mobile operator of the wireless user wherein said first GSM based IMSI request message requests said IMSI of said wireless user; and
b) receive at said second interface a first GSM based response message comprising said IMSI of said wireless user.

### Claim 5 (depends on 1)

The system of claim 1 wherein said processor is further configured to:
a) receive at said first interface an HTTP formatted balance request message from said source, said HTTP formatted balance request message indicating said IMSI or a Mobile Subscriber Integrated Services Digital Network (“MSISDN”);
b) generate at said second interface to said mobile operator a GSM based USSD message conveying a balance request to said mobile operator, wherein said GSM based USSD message indicates said IMSI;
c) receive at said second interface a GSM based USSD message from mobile operator indicating a balance of said account associated with said wireless user; and
d) generate at said first interface an HTTP formatted balance response message to said source indicating said balance and said IMSI or MSISDN.

### Claim 6 (depends on 1)

The system of claim 1 wherein said processor is further configured to:
a) receive a create-menu request message from said source at said first interface to generate a menu on said mobile device of said user, wherein said create-menu request message comprises a plurality of options available to said wireless user regarding a purchase; and
b) generate a USSD based create-menu request message to said mobile operator, wherein said create-menu request message comprising said plurality of options;
c) receive a USSD based create-menu response message comprising one of said plurality of options; and
d) generate a create-menu response message on said first interface to said source where said create-menu response comprises one of said plurality of options.

### Claim 7 (depends on 1)

The system of claim 1 wherein said identifier associated with said wireless user comprises a mobile telephone number.

### Claim 8

A method for processing payment related requests associated with a wireless user comprising the steps of:
a) receive at a processor from a first interface from a source a first charge request message requesting a charge operation to an account associated with a wireless user, said first charge request message comprising a first HTTP formatted message comprising both an identifier associated with said wireless user and a charge amount;
b) generate by said processor at a second interface to a mobile operator a first GSM based request message comprising a first Unstructured Supplementary Service Data (“USSD”) message requesting said charge operation and indicating said charge amount, said first GSM based request message comprising an International Mobile Subscriber Identity (“IMSI”) associated with said wireless user;
c) receive by said processor at said second interface a first GSM based response message comprising a second USSD message received in response to said first GSM based request message, wherein said first GSM based response message confirms said charge to said account by said mobile operator; and
d) generate by said processor at said first interface a first charge response message to said source comprising a second HTTP formatted message confirming said charge to said account by said mobile operator.

### Claim 9 (depends on 8)

The method of claim 8 further comprising the step of:
retrieving from a memory by said processor a data string associated with said mobile operator of said wireless user, said data string defined as indicating said charge operation to said mobile operator, wherein said processor incorporates said data string into said first USSD message.

### Claim 10 (depends on 9)

The method of claim 9 further comprising the step of:
receive at said processor from said first interface a second request message from said source comprising a third HTTP formatted message, wherein said second request message comprises a mobile telephone number of said wireless user.

### Claim 11 (depends on 10)

The method of claim 10 further comprising the steps of:
e) generate by said processor at said second interface a first GSM based request message comprising said mobile telephone number to said mobile operator of the wireless user wherein said first GSM based request message requests said IMSI of said wireless user; and
f) receive at said processor from said second interface a first GSM based response message comprising said IMSI of said wireless user.

### Claim 12 (depends on 11)

The method of claim 11 wherein said steps e) and f) occur after step a) and before step b).

### Claim 13 (depends on 8)

The method of claim 8 further comprising the steps of:
a) receive at said first interface an HTTP formatted balance request message from said source, said HTTP formatted balance request message comprising said IMSI or a MSISDN;
b) generate at said second interface to said mobile operator a GSM based USSD message conveying a balance request to said mobile operator, wherein said GSM based USSD message indicates said IMSI;
c) receive at said second interface a GSM based USSD message from said mobile operator indicating said balance; and
d) generate at said first interface an HTTP formatted balance response message to said source indicating said balance and an IMSI or MSISDN indicating parameter.

### Claim 14 (depends on 8)

The system of claim 8 wherein said processor is further configured to:
a) receive a “create menu” request message from said source at said first interface to generate a menu on said mobile device of said user, wherein said “create menu” request message comprises a plurality of options available to said wireless user regarding a purchase;
b) generate a USSD based “create menu” request message to said mobile operator, wherein said “create menu” request message comprising said plurality of options;
c) receive a USSD based “create menu” response message comprising one of said plurality of options; and
d) generate a “create menu” response message on said first interface to said source where said “create menu” response comprises one of said plurality of options.

### Claim 15 (depends on 8)

The system of claim 8 wherein said an identifier associated with said wireless user comprises a mobile telephone number.

### Claim 16

A non-transitory computer readable medium comprising instructions for instructing a processor to perform the steps of:
a) receive from a first interface from a source a first charge request message requesting a charge operation to an account associated with a wireless user, said first charge request message comprising a first HTTP formatted message comprising an identifier associated with said wireless user and a charge amount;
b) generate at a second interface to a mobile operator a first GSM based request message comprising a first USSD message requesting said charge operation and said charge amount, said first GSM based request message comprising an IMSI associated with said wireless user;
c) receive at said second interface a first GSM based response message comprising a second USSD message received in response to said first GSM based request message, wherein said first GSM based response message confirms said charge to said account by said mobile operator; and
d) generate at said first interface a first charge response message to said source comprising a second HTTP formatted message confirming said charge to said account by said mobile operator.

### Claim 17 (depends on 16)

The non-transitory computer readable medium of claim 16 further comprising the step of:
retrieve from a memory a data string associated with said mobile operator of said wireless user, said data string defined as indicating said charge operation to said mobile operator, wherein said processor incorporates said data string into said first USSD message.

### Claim 18 (depends on 17)

The non-transitory computer readable medium of claim 17 further comprising the step of:
receive from said first interface a second request message from said source comprising a third HTTP formatted message, wherein said second request message comprises a mobile telephone number of said wireless user.

### Claim 19 (depends on 18)

The non-transitory computer readable medium of claim 18 further comprising the steps of:
a) generate by said processor at said second interface a first GSM based request message comprising said mobile telephone number to said mobile operator of the wireless user wherein said first GSM based request message requests an International Mobile Subscriber Identifier (“IMSI”) of said wireless user; and
b) receive at said processor from said second interface a first GSM based response message comprising said IMSI of said wireless user.

### Claim 20 (depends on 19)

The non-transitory computer readable medium of claim 19 further comprising the steps of:
a) receive at said first interface an HTTP formatted balance request message from said source, said HTTP formatted balance request message comprising said IMSI or a MSISDN;
b) generate at said second interface to said mobile operator a GSM based USSD message indicating a balance request to said mobile operator, wherein said GSM based USSD message indicates said IMSI;
c) receive at said second interface a GSM based USSD message from mobile operator indicating a balance; and
d) generate at said first interface an HTTP formatted balance response message to said source indicating said balance and said IMSI or said MSISDN.
