US 9,003,079 B2 · API methods for phone-on-file opt-in at a merchant server

Abstract

A phone-on-file opt-in method is described. A phone-on-file opt-in request is received at the billing server including a msisdn and a merchant supplied unique consumer identifier. The billing server confirms the phone-on-file opt-in with a consumer device and records a phone-on-file opt-in status as active if the first phone-on-file is confirmed. A charge method includes receiving, at the billing server, a charge API call from a merchant server including at least one identifier and an amount, determining a phone-on-file opt-in status corresponding to the identifier at the billing server and transmitting a request to charge a user account to a carrier server if the phone-on-file opt-in status is active, but not if the phone-on-file opt-in status is inactive, the request including an amount corresponding to the amount received in the charge API call.

Claims15

Dependent claims

A method of managing transactions with a merchant server comprising:

a) executing a phone-on-file opt-in method with the merchant server, including:
receiving a msisdn from a consumer device at the merchant server;
transmitting a first phone-on-file opt-in request from the merchant server to a billing server, including the msisdn and a merchant-id being a billing server assigned merchant identifier value;
receiving a PIN code from the consumer device;
transmitting a second phone-on-file opt-in request from the merchant server to the billing server, including the PIN code, a phone-on-file opt-in being recorded as active against the merchant-id by the billing server;
and
receiving a response from the billing server at the merchant server indicating whether the PIN code is verified or invalid;
and
b) executing a charge method with the merchant server including;
transmitting a charge API call from the merchant server to the billing server if the PIN code is verified but not if the PIN code is invalid, the charge API call including an amount and an identifier for the billing server to determine a phone-on-file opt-in status corresponding to the identifier;
and
receiving a charge result callback notification from the billing server at the merchant server indicating whether a user account at a carrier server has been charged by the billing server.

9 more elements

A merchant server comprising:

a processor;
a computer-readable medium connected to the processor;
and
a set of instructions on the computer-readable medium and executable by the processor, including:
a user interface transmitted to a consumer device with a msisdn field for entry of a msisdn and receivable by the processor and transmitted to a billing server in a first phone-on-file opt-in request and a PIN code field for entry of a PIN code and receivable by the processor and transmitted to the billing server in a second phone-on-file opt-in request;
and
a recurring billing management module executing a charge method including:
transmitting a charge API call from the merchant server to the billing server if the PIN code is verified but not if the PIN code is invalid, the charge API call including an amount and an identifier for the billing server to determine a phone-on-file opt-in status corresponding to the identifier;
receiving a charge result call back notification from the billing server at the merchant server indicating whether a user account at a carrier server has been charged by the billing server;
and
a) executing a phone-on-file opt-in method with the merchant server, including:
receiving a msisdn from a consumer device at the merchant server;
transmitting a first phone-on-file opt-in request from the merchant server to a billing server, including the msisdn;
receiving a PIN code from the consumer device;
transmitting a second phone-on-file opt-in request from the merchant server to the billing server, including the PIN code;
and
receiving a response from the billing server at the merchant server indicating whether the PIN code is verified or invalid;
b) executing a charge method with the merchant server including:
transmitting a charge API call from the merchant server to the billing server if the PIN code is verified but not if the PIN code is invalid, the charge API call including an amount and an identifier for the billing server to determine a phone-on-file opt-in status corresponding to the identifier;
and
receiving a charge result callback notification from the billing server at the merchant server indicating whether a user account at a carrier server has been charged by the billing server;
and
executing a cancel method at the merchant server, including transmitting a view of a user interface from the merchant server to a consumer device, the view allowing for selection to cancel the subscription, receiving a call to cancel the subscription via the interface from the consumer device at the merchant server, and making a cancel-phone-on-file opt-in API call from the merchant server to the billing server to update the phone-on-file opt-in to inactive.

20 more elements

Dependencies are inferred from the claim text.

API methods for phone-on-file opt-in at a merchant server

Life of this patent

API methods for phone-on-file opt-in at a merchant server

Life of this patent

Abstract

Claims15