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.

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.

Abstract: The billing gateway charge method and system are disclosed. A charge is processed by receiving a charge API call from a merchant server, detecting a select carrier server from a plurality of servers, transmitting a charge request to the select carrier server, and returning a charge result callback notification to the merchant server. If the charge request fails, the merchant server can submit a new request and an indication of acceptance and failure of the charge request is returned to the merchant server based on the new requests provided that the new request has a new request-id. A continue method allows for managing consumer opt-in in order to complete a transaction. Once the transaction is completed, a refund request from the merchant server can be processed by transmission to the carrier 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.

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.

Abstract: A method and system of processing a sale of an article, a virtual article, a service or a functionality such as a game is described. A code is generated by a server. A charge request is transmitted to an account server to charge an account of a user for a value of the code. The code is transmitted to a user device. The code is then processed by redeeming the code, wherein redemption of the code includes receiving the code from a user device and in response allowing access to the user device to the article, virtual article, a service or a functionality.

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.

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.

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.

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.

Abstract: The billing gateway charge method and system are disclosed. A charge is processed by receiving a charge API call from a merchant server, detecting a select carrier server from a plurality of servers, transmitting a charge request to the select carrier server, and returning a charge result callback notification to the merchant server. If the charge request fails, the merchant server can submit a new request and an indication of acceptance and failure of the charge request is returned to the merchant server based on the new requests provided that the new request has a new request-id. A continue method allows for managing consumer opt-in in order to complete a transaction. Once the transaction is completed, a refund request from the merchant server can be processed by transmission to the carrier server.

Abstract: A transaction is authorized by receiving an authorize API call from a merchant server, detecting a select carrier server, and transmitting an authorize request to the select carrier server. The carrier server will then reserve an amount of funds based on the authorization request. The authorized transaction is then recorded based on the authorize request. The consumer may then request to cancel the transaction. If a capture request is received, a determination is made whether the cancel request has been received and whether the authorized transaction has been cancelled. If the transaction has not been cancelled, a billing request is transmitted to the carrier server so that the carrier server charges for the transaction.

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.

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.

Abstract: An electromagnetic display element is controlled by one or more high remanence cores which have control windings. A circuit is connectable to an A.C. outlet and provides to the windings a D.C. pulse in one sense (to switch the display element in one direction) when the circuit is connected to the A.C. outlet. The circuit included a capacitor charged during such connection. The circuit is designed so that, on its disconnection from the A.C. outlet, the capacitor discharges through the winding in the opposite sense and switches the display element in the opposite direction.