Merchant managed subscriptions at a 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 billing server comprising:

• a) executing an opt-in method with the billing server, including:
• receiving a first opt-in request at the billing server including a msisdn;
• generating, with the billing server, a PIN code;
• transmitting, with the billing server, a text message to a consumer mobile phone at the msisdn with the PIN code;
• receiving a second opt-in request at the billing server, including a PIN code;
• verifying, at the billing server, the PIN code received in the second opt-in request against the PIN code transmitted in the text message;
• and
• recording, at the billing server, an opt-in status as active for the msisdn within a data structure if the PIN code is verified;
• and
• b) executing a charge method with the billing server including:
• receiving, at the billing server, a charge API call from a merchant server at the billing server, including at least one identifier and an amount;
• determining an opt-in status corresponding to the identifier within the data structure at the billing server;
• and
• transmitting a request to charge a user account to a carrier server if the opt-in status is active, but not if the opt-in status is inactive, the request including an amount corresponding to the amount received in the charge API call.

A billing 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:
• an SMS messaging module;
• a consumer opt-in management module executing an opt-in method including:
• receiving a first opt-in request including a msisdn;
• generating a PIN code;
• transmitting, using the SMS messaging module, a text message to a consumer mobile phone at the msisdn with the PIN code;
• receiving a second opt-in request including a PIN code;
• verifying the PIN code received in the second opt-in request against the PIN code transmitted in the text message;
• and
• recording an opt-in status as active within a data structure for the msisdn if the PIN code is verified;
• and
• a carrier billing module executing a charge method including:
• receiving a charge API call from a merchant server, including at least one identifier and an amount;
• determining an opt-in status corresponding to the identifier in the data structure;
• and
• transmitting a request to charge a user account to a carrier server if the opt-in status is active, but not if the opt-in status is inactive, the request including an amount corresponding to the amount received in the charge API call.