Subscription managed method and system for text-to-pay subscriptions at a subscription server

• US 10,546,331 B2
• Filed: 08/25/2017
• Issued: 01/28/2020
• Est. Priority Date: 10/16/2013
• Status: Active Grant

• Current Assignee: Boku Incorporated
• Original Assignee: Boku Incorporated
• Inventors: Steif, Daniel, Davis, Kurt, Holden, Katherine Corner, Nebrich, Samantha Elena
• Primary Examiner(s): Yu, Ariel J
• Application Number:
  US15/686,603
• Publication Number:
  US 20170352074A1
• Time in Patent Office: 886 Days
• Field of Search: None
• CPC Class Codes: G06Q 20/14 specially adapted for billing systems
• CPC Class Codes: G06Q 20/16 Payments settled via telecommunication systems
• CPC Class Codes: G06Q 20/32 using wireless devices
• CPC Class Codes: G06Q 20/3255 using mobile network messaging services for payment, e.g. SMS
• CPC Class Codes: G06Q 20/4012 Verifying personal identification numbers [PIN]
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements

Abstract

A subscription identifier is communicated between the billing server and subscription server. The billing server receives a subscription identifier text message from the user device. The billing server identifies a carrier server from the subscription identifier text message. The billing server receives an authorization text message from the user device in response to an authorization request text message and charges an account of the carrier server that has been identified. If the charge has been successful, then the billing server transmits a renewal notification text message to the subscription server. The subscription server updates an account having the subscription identifier to reflect a new expiration.

Claims

1. A method of managing subscriptions with a subscription server comprising:

a) executing an opt-in method with the subscription server, after a billing server receives a first opt-in request at the billing server, the first op-in request being a text message from a user mobile phone at a msisdn, the billing server generates a PIN code, and the billing server transmits a text message to a user mobile phone at the msisdn with the PIN code, including;

receiving a PIN code from the consumer device;

transmitting a second opt-in request from the subscription server to the billing server, including the PIN code received from the consumer device; and

receiving a response from the billing server at the subscription server indicating whether the PIN code is verified or invalid, an opt-in being recorded as active against the subscription-id if the PIN code is verified; and

b) executing a charge method with the subscription server including;

transmitting a charge API call from the subscription server to the billing server if the opt-in is active but not if the opt-in is inactive, the charge API call including an amount and an identifier for the billing server to determine an opt-in status corresponding to the identifier;

receiving a charge result callback notification from the billing server at the subscription server indicating whether a user account at a carrier server has been charged by the billing server; and

updating the expiration of the identifier to a later expiration in response to the chargeresult callback notification.

2. The method of claim 1, wherein the text message of the first op-in request includes a uniform resource locator that is selectable by a user to request a registration page from the subscription server, further comprising:

transmitting user interface from the subscription server to the user mobile phone in response to the user selecting the uniform resource locator, the user interface including a PIN code field for entry of a PIN code.

3. The method of claim 1, wherein the msisdn has a plurality of subscription-id'"'"'s, each having a separate opt-in parameter that is set in a selectable manner to active or inactive.

4. The method of claim 1, wherein the second opt-in request includes a user-id being a merchant provided unique user identifier, a country being a country code in ISO 3166-1-alpha-2 standard, an item-description being an exact quantity and name of the item(s) being purchased, a merchant-id being a billing server assigned merchant identifier value, a msisdn being a subscriber mobile phone number in international MSISDN format, a service-id being a merchant offering identifier, a subscription-id being a merchant assigned unique identifier for the user subscription and subscription-terms.

5. The method of claim 1, wherein the charge API call includes a user-id, a user-ip-address being an originating IP address of the user, a country being a country code in ISO 3166-1-alpha-2 standard, a currency being an ISO 4217 3 letter currency code, an end-merchant-id being a billing server assigned merchant identifier for an end merchant submitting transactions via a reseller, an item-description being a product disclosure describing the quantity and type of item being purchased, a merchant-id being a billing server assigned merchant identifier value, a msisdn being a Subscriber mobile phone number in international MSISDN format:

country code+mobile phone number, request-id being a unique merchant assigned request ID, a subscription frequency being a frequency of subscription renewal, a subscription-id being a merchant assigned unique identifier for the user subscription, a service-id being a merchant offering identifier and total-amount being a total amount charged including tax.

6. The method of claim 5, wherein the chargeresult callback notification includes a user-auth-required being a billing server assigned charge identifier, a result-code being a result code for this request and a result-message being a human readable description of the result.

7. The method of claim 1, further comprising:

c) executing a remind-charge method with the subscription server after the opt-in method and before the charge method, including;

transmitting a remind-charge from the subscription server to the billing server; and

sending a text message from the billing server to the user mobile phone that contains terms of a subscription and a due date for when the charge method will be executed, the charge method being executed on the due date.

8. The method of claim 7, wherein the remind-charge request includes a user-id being a subscription provided unique user identifier, a country being a country code in ISO 3166-1-alpha-2 standard, an item-description being an exact quantity and name of the item(s) being purchased a merchant-id being a billing server assigned merchant identifier value, a msisdn being a subscriber mobile phone number in international MSISDN format:

country code+mobile phone number, a renewal-date being a start date of next subscription cycle, a service-id being a merchant offering identifier, a subscription-id being a merchant assigned unique identifier for the user subscription, and subscription-terms.

9. The method of claim 1, further comprising:

d) executing a cancel method at the subscription server, including;

transmitting a view of a user interface from the subscription 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 subscription server; and

making a cancel-opt-in API call from the subscription server to the billing server to update the opt-in to inactive.

10. The method of claim 1, wherein the billing server receives payment from the account server in response to the charge request, further comprising:

receiving, with the subscription server, a payment from the billing server in response to the billing server receiving the payment from the account server.

11. The method of claim 1, wherein the billing server transmits a charge request to the carrier server, the charge request including an amount to be charged to the account of the carrier server.

12. The method of claim 11, further comprising:

receiving, with the billing server, a confirmation from the account server that the account has been charged, wherein the billing server only transmits the second text message if the confirmation has been received.

13. The method of claim 1, wherein the billing server receives a phone number of the user, the account at the carrier server being an account identified by the phone number on the carrier server.

14. The method of claim 13, wherein the text message of the first op-in request includes the phone number.

15. The method of claim 13, wherein the text message of the first op-in request includes an identification of the carrier server.

16. A non-transitory 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 subscription server comprising:

a) executing an opt-in method with the subscription server, after a billing server receives a first opt-in request at the billing server, the first op-in request being a text message from a user mobile phone at a msisdn, the billing server generates a PIN code, and the billing server transmits a text message to a user mobile phone at the msisdn with the PIN code, including;

receiving a PIN code from the consumer device;

transmitting a second opt-in request from the subscription server to the billing server, including the PIN code received from the consumer device; and

receiving a response from the billing server at the subscription server indicating whether the PIN code is verified or invalid, an opt-in being recorded as active against the subscription-id if the PIN code is verified; and

b) executing a charge method with the subscription server including;

transmitting a charge API call from the subscription server to the billing server if the opt-in is active but not if the opt-in is inactive, the charge API call including an amount and an identifier for the billing server to determine an opt-in status corresponding to the identifier;

receiving a charge result callback notification from the billing server at the subscription server indicating whether a user account at a carrier server has been charged by the billing server; and

updating the expiration of the identifier to a later expiration in response to the chargeresult callback notification.

17. A subscription 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 after a billing server receives a first opt-in request at the billing server, the first op-in request being a text message from a user mobile phone at a msisdn, the billing server generates a PIN code, and the billing server transmits a text message to a user mobile phone at the msisdn with the PIN code, the user interface including 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, the processor receiving a response from the billing server at the subscription server indicating whether the PIN code is verified or invalid, an opt-in being recorded as active against the subscription-id if the PIN code is verified; and

a recurring billing management module executing a charge method including;

transmitting a charge API call from the subscription server to the billing server if the opt-in is active but not if the opt-in is inactive, the charge API call including an amount and an identifier for the billing server to determine an opt in status corresponding to the identifier;

receiving a charge result call back notification from the billing server at the subscription server indicating whether a user account at a carrier server has been charged by the billing server; and

updating the expiration of the identifier to a later expiration in response to the chargeresult callback notification.