1. A dual-bladed scraper comprising:
an elongated handle having handle upper and lower surfaces extending along a longitudinal handle axis between a proximal end including a grip portion configured for gripping by a user’s hand and a distal end extending forwardly of the proximal end; and
a blade-retaining head mounted to the distal end for pivotal movement, relative to the handle, about a head-rotation axis and having opposed first and second ends mutually situated on opposite sides of the head-rotation axis and being configured for the removable retention of, respectively, first and second scraping blades each of which first and second scraping blades has at least one scraping edge, the blade-retaining head being pivotable about the head-rotation axis between a first angular position in which the first blade is in a deployed attitude and the second blade is in a non-deployed attitude in which the second blade is at least partially shrouded beneath the handle lower surface and a second angular position in which the second blade is in a deployed attitude and the first blade is in a non-deployed attitude in which the first blade is at least partially shrouded beneath the handle lower surface.
2. The scraper of claim 1 wherein at least a portion of the distal end of the handle is laterally flared relative to the grip portion to define a blade shroud configured such that, when each of first and second scraping blades retained by, respectively, the first and second ends is alternatively in the non-deployed attitude, the at least one scraping edge of that non-deployed blade is entirely shrouded by the blade shroud as viewed from above the handle upper surface.
3. The scraper of claim 2 wherein the first and second ends of the blade- retaining head comprise, respectively, first and second blade mounts defining, respectively, first and second blade planes that are mutually non-coplanar and non-parallel.
4. The scraper of claim 1 wherein the first and second ends of the blade- retaining head comprise, respectively, first and second blade mounts defining, respectively, first and second blade planes that are mutually non-coplanar and non-parallel.
5. A dual-bladed scraper comprising:
an elongated handle having handle upper and lower surfaces extending along a longitudinal handle axis between a proximal end including a grip portion configured for gripping by a first hand of a user and a distal end extending forwardly of the proximal end and grip portion; and
a blade-retaining head mounted to the distal end for pivotal movement, relative to the handle, about a head-rotation axis and having opposed first and second ends mutually situated on opposite sides of the head-rotation axis and including, respectively, first-blade and second-blade mounts removably retaining, respectively, a first scraping blade with a first-blade scraping edge and second scraping blade with a second-blade scraping edge, the blade-retaining head being pivotable about the head-rotation axis between a first angular position in which the first blade is in a deployed attitude and the second blade is in a non- deployed attitude in which the second-blade scraping edge is at least partially shrouded beneath the handle lower surface and a second angular position in which the second blade is in a deployed attitude and the first blade is in a non- deployed attitude in which the first-blade scraping edge is at least partially shrouded beneath the handle lower surface.
6. The scraper of claim 5 wherein a portion of the distal end of the handle is laterally flared in order to define a blade shroud configured such that, when each of the first and second scraping blades is in the non-deployed attitude, the entire scraping edge of that non-deployed scraping blade is shrouded by the blade shroud as viewed from above the handle upper surface.
7. The scraper of claim 6 wherein the first-blade and second-blade mounts include, respectively, first and second blade-supporting surfaces that define, respectively, first and second blade planes that are mutually non-coplanar and non-parallel.
8. The scraper of claim 5 wherein the first-blade and second-blade mounts include, respectively, first and second blade-supporting surfaces that define, respectively, first and second blade planes that are mutually non-coplanar and non-parallel.
9. The scraper of claim 8 wherein the first and second blade planes are pitched such that they mutually diverge downwardly away from the distal end of the handle and the head rotation axis.
10. The scraper of claim 9 wherein the blade-retaining head is of generally arcuate configuration.
11. The scraper of claim 8 wherein a portion of the distal end of the handle is laterally flared in order to define a blade shroud configured such that, when each of the first and second scraping blades is in the non-deployed attitude, the entire scraping edge of that non-deployed scraping blade is shrouded by the blade shroud as viewed from above the handle upper surface.
12. The scraper of claim 11 wherein the first and second blade planes are pitched such that they mutually diverge downwardly away from the distal end of the handle and the head rotation axis.
13. The scraper of claim 12 wherein the blade-retaining head is of generally arcuate configuration.
14. The scraper of claim 5 wherein the scraping edge of a scraping blade in a deployed attitude extends transversely to the longitudinal handle axis.
15. A dual-bladed scraper comprising:
a handle having handle upper and lower surfaces; and
a blade-retaining head mounted to the handle for pivotal movement between first and second angular positions about a head-rotation axis and having opposed first and second ends situated on mutually opposite sides of the head- rotation axis;
a first scraping blade retained by the first end of the blade-retaining head and having a first-blade scraping edge; and
a second scraping blade retained by the second end of the blade-retaining head and having a second-blade scraping edge, wherein
(i) the first angular position is such the first blade is in a deployed attitude and the second-blade scraping edge is shrouded beneath the handle in a non-deployed attitude; and
(ii) the second angular position is such that the second blade is in a deployed attitude and the first-blade scraping edge is shrouded beneath the handle in a non-deployed attitude.
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A method of processing a charge comprising:
receiving, with a billing server, an authorize API call with an authorize request from a merchant server, including a msisdn and an amount;
determining, with the billing server, a select carrier server from a plurality of carrier servers;
transmitting, with the billing server, an authorize request to the select carrier server based on the amount;
recording, with the billing server, an authorized transaction based on the authorize request;
receiving, with the billing server, a capture API call with a capture request after transmitting the authorize request to the select carrier server;
determining, with the billing server, in response to the capture request, whether a cancel request has been received from the merchant server after the authorize request and before the capture request and the capture transaction has been cancelled; and
transmitting, with the billing server, in response to the capture request, a billing request to the select carrier server if the captured transaction has not been cancelled but not if the captured transaction has been cancelled.
2. The method of claim 1, wherein the authorize API call and capture API call are received at least one URL at the billing server.
3. The method of claim 1, wherein the authorize API call and capture API call are received at different URL’s at the billing server.
4. The method of claim 1, wherein the select carrier server is deleted from the authorize API call that includes at least one of a name of a carrier, a mcc (mobile country code), a mnc (mobile network code).
5. The method of claim 1, wherein the authorize API call includes a merchant-id (billing server assigned merchant ID), consumer-ip-address (IP address of the originating consumer), a service-id (merchant server offering ID), a country (country code), a currency (currency code), an item-description (description of the item being purchased), and a request-id (merchant server assigned request ID).
6. The method of claim 1, further comprising:
transmitting, with the billing server, an authorization response to the merchant server after transmitting the authorize request to the select carrier server but before receiving the capture request.
7. The method of claim 6, wherein the authorization response includes an authorization-id (billing server assigned authorization ID), a result-code (the result of this request), and a result message (description of the result).
8. The method of claim 1, wherein the capture request includes a merchant-id (billing server assigned merchant ID), an authorization-id (billing server assigned authorization ID), and a request-id (merchant server assigned request ID. Must be unique.).
9. The method of claim 1, further comprising:
transmitting, with the billing server, a capture response notification to the merchant server after transmission of the billing request to the select carrier server.
10. The method of claim 9, wherein the capture response includes a capture-id (unique ID for this capture request), a result-code (the result of this request), and a result message (description of the result).
11. The method of claim 1, further comprising:
receiving, with the billing server, a cancel request from the merchant server;
cancelling, with the billing server, the captured transaction to disallow transmission of the billing request; and
transmitting, with the billing server, a cancel response to the merchant server following the cancelling of the captured transaction.
12. The method of claim 11, wherein the cancel request includes a merchant-id (billing server assigned merchant ID), an authorization-id (billing server assigned authorization ID), and a request-id (merchant server assigned request ID).
13. The method of claim 12, wherein the cancel response includes a result-code (the result of this request), and a result message (description of the result).
14. The method of claim 1, further comprising:
receiving, with the billing server, a refund call from the merchant server;
determining, with the billing server, the select carrier server in response to the refund call;
transmitting, with the billing server, a refund request to the select carrier in response to the refund call from the merchant server, including an amount; and
transmitting, with the billing server, a chargeback notification to the merchant server in response to the refund call from the merchant server.
15. The method of claim 14, wherein the chargeresult callback notification has a capture-id and the refund call has the capture-id of the chargeresult callback notification.
16. The method of claim 14, further comprising:
determining, with the billing server, whether a valid reason code is included in the refund call, the refund request only being transmitted if a valid reason code is included in the refund call.
17. The method of claim 14, wherein the refund call includes a merchant-id (billing server assigned merchant ID), a capture-id (capture ID of the payment to refund), a reason-code (billing server reason code), and a request-id (merchant server assigned request ID).
18. The method of claim 14, wherein the chargeback notification includes a refund-id (ID of the billing server created refund transaction), a result-code (the result of this request), and a result-message (description of the result).
19. 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 processing a charge comprising:
receiving, with a billing server, an authorize API call with an authorize request from a merchant server, including a msisdn and an amount;
determining, with the billing server, a select carrier server from a plurality of carrier servers;
transmitting, with the billing server, an authorize request to the select carrier server based on the amount;
recording, with the billing server, an authorized transaction based on the authorize request;
receiving, with the billing server, a capture API call with a capture request after transmitting the authorize request to the select carrier server;
determining, with the billing server in response to the capture request, whether a cancel request has been received from the merchant server after the authorize request and before the capture request and the capture transaction has been cancelled; and
transmitting, with the billing server, in response to the capture request, a billing request to the select carrier server if the captured transaction has not been cancelled but not if the captured transaction has been cancelled.
20. A billing computer system comprising:
a processor;
a computer-readable medium connected to the processor; and
a set of instructions on the computer-readable medium, including:
an authorization management module storing consumer authorizations; and
a carrier billing module connected to the authorization management module and executable by the processor to receive an authorize API call with an authorize request from a merchant server, including a msisdn and an amount, to determine a select carrier server from a plurality of carrier servers, to transmit an authorize request to the select carrier server based on the amount, to record an authorized transaction based on the authorize request, to receive a capture API call with a capture request after transmitting the authorize request to the select carrier server, to determine in response to the capture request, whether a cancel request has been received from the merchant server after the authorize request and before the capture request and the capture transaction has been cancelled and to transmit in response to the capture request, a billing request to the select carrier server if the captured transaction has not been cancelled but not if the captured transaction has been cancelled.