Merchant managed subscriptions at a merchant server
AssigneeBoku, Inc.
InventorsJohn P. Browne, James C. McIntyre, Marcin L. Pawlowski
Life of this patent
Estimating the term…
Abstract
A system and method is described for managing subscriptions between a consumer mobile phone, merchant server, billing server and carrier server. A charge-info method is used for the merchant server to retrieve charge elements from the billing server for constructing a user interface for the consumer mobile phone. An opt-in method is used to confirm a consumer's opt-in for a subscription. A remind-charge method is used to remind the consumer of an upcoming charge on the subscription. A charge method allows the merchant server to charge a user account on a carrier server via the billing server. A cancel method is used for the consumer to cancel the subscription.
Claims15
A method of managing subscriptions with a merchant server comprising:
- a) executing an opt-in method with the merchant server, including:
- receiving a msisdn from a consumer device at the merchant server;
- transmitting a first 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 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;
- 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 an opt-in status corresponding to the identifier;
- and
- receiving a chargeresult 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.
A computer-readable medium having stored thereon a set of instructions which, when executed by a processor of a computer performs a method of managing subscriptions with a merchant server comprising:
- a) executing an opt-in method with the merchant server, including:
- receiving a msisdn from a consumer device at the merchant server;
- transmitting a first 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 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;
- 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 an opt-in status corresponding to the identifier;
- and
- receiving a chargeresult 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.
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 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 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 an opt-in status corresponding to the identifier;
- and
- receiving a chargeresult 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.
Dependencies are inferred from the claim text.