1-9. (canceled)
10. An outboard motor comprising:
an engine including a cylinder body and a cylinder head that are aligned in a frontrear direction;
a catalyst held by the engine; and
a catalyst housing portion provided at a side portion of the cylinder head; wherein
the engine includes an exhaust port provided in the cylinder head, a first exhaust passage arranged to guide exhaust discharged from the exhaust port into an interior of the catalyst housing portion, and a passage defining member defining a second exhaust passage arranged such that exhaust that has passed through the interior of the catalyst housing portion flows into the second exhaust passage; and
the catalyst is held by the engine in a state in which at least a portion of the catalyst is housed in the interior of the catalyst housing portion.
11. The outboard motor according to claim 10, wherein the cylinder head includes a mating surface in contact with the cylinder body;
the catalyst housing portion includes an attachment surface disposed on a same plane as the mating surface; and
the catalyst is attached to the attachment surface.
12. The outboard motor according to claim 10, wherein the engine includes a coupling member coupled to the cylinder head, and the first exhaust passage includes the cylinder head and the coupling member.
13. The outboard motor according to claim 10, wherein the engine includes a plurality of cylinders that are aligned vertically;
the first exhaust passage includes a plurality of passages respectively connected to the plurality of cylinders; and
the passage connected to the cylinder that is positioned lowest is independent of the passages connected to the other cylinders.
14. The outboard motor according to claim 10, wherein the engine includes a plurality of cylinders that are aligned vertically;
the first exhaust passage includes a plurality of passages respectively connected to the plurality of cylinders; and
at least one passage among the plurality of passages includes a hole provided in the cylinder head.
15. The outboard motor according to claim 10, wherein the passage defining member includes a first member arranged to house a portion of the catalyst, and a second member coupled to the first member.
16. The outboard motor according to claim 10, further comprising a drain passage connected to the first exhaust passage at an upstream side of the catalyst.
17. The outboard motor according to claim 16, wherein the drain passage is connected to a lowermost portion of the first exhaust passage.
18. The outboard motor according to claim 10, wherein the catalyst housing portion is arranged such that exhaust flows inside the catalyst housing portion in the frontrear direction.
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 computing device configured to perform actions for processing a payment authorization request, wherein the actions comprise:
receiving, by the computing device from a merchant point-of-sale device, a payment authorization request, wherein the payment authorization request includes a payment token;
transmitting, by the computing device, a validation request to a mobile token validation module;
receiving, by the computing device, payment account information from the mobile token validation module in response to the validation request;
transmitting, by the computing device to a payment processor, a payment authorization request based on the payment account information; and
transmitting, by the computing device to the merchant point-of-sale device, a payment authorization response, the payment authorization response including a persistent token.
2. The computing device of claim 1, wherein the actions further comprise storing the persistent token in a persistent token data store.
3. The computing device of claim 1, wherein the payment authorization request and the validation request include an associated payment type, and wherein the payment account information is associated with the payment token and the associated payment type.
4. The computing device of claim 3, wherein the payment token is associated with a mobile wallet, wherein the mobile wallet stores payment account information associated with a plurality of payment accounts, and wherein the associated payment type is associated with a selected one of the plurality of payment accounts.
5. The computing device of claim 1, wherein the actions further comprise:
transmitting, by the computing device, a payment authorization response to the merchant point-of-sale device in response to a notification received from the payment processor.
6. The computing device of claim 5, wherein the payment authorization response includes a portion of the payment account information.
7. The computing device of claim 1, wherein the actions further comprise detecting the payment token as being for use with a mobile wallet registry system.
8. A system for managing mobile tokens, the system comprising:
a mobile token data store configured to store token records, each token record including a mobile token and an associated wallet identifier;
a mobile token validation module communicatively coupled to the mobile token data store and configured to:
receive a validation request from a requestor, the validation request including a mobile token and a payment type indication;
retrieve a wallet identifier associated with the mobile token from a token record in the mobile token data store;
retrieve payment account information from a configuration portal server using the mobile token and the payment type indication; and
transmit the payment account information to the requestor.
9. The system of claim 8, wherein the requestor is a payment gateway module.
10. The system of claim 8, wherein the requestor is an issuer processor system.
11. The system of claim 8, wherein the mobile token data store is configured to store a plurality of token records each including a different mobile token and a given associated wallet identifier.
12. The system of claim 8, wherein each token record includes addressing information.
13. The system of claim 8, further comprising a mobile token generation module configured to:
generate a token in response to a token request, the token request including a wallet identifier; and
store a token record including the token and the wallet identifier in the mobile token data store.
14. The system of claim 13, wherein the token request is received from a configuration portal server, and wherein the mobile token generation module is further configured to transmit the token to the configuration portal server.
15. The system of claim 13, wherein the token request is received from a mobile device, and wherein the mobile token generation module is further configured to transmit the token to the mobile device.
16. The system of claim 8, further comprising a policy and fraud detection module configured to enforce wallet policies and detect fraud patterns.
17. The system of claim 16, wherein wallet policies include one or more of a spending limit per token, a token expiration date, a token window, allowable merchant categories, and token velocity.
18. The system of claim 16, wherein the mobile token data store is further configured to store wallet policies.
19. A computer-implemented method for configuring and using a mobile wallet, the method comprising:
receiving, by a configuration portal server, a wallet boarding request from a requesting device, wherein the wallet boarding request includes a mobile device identifier;
creating, by the configuration portal server, a sponsor wallet in a sponsor wallet data store, the sponsor wallet including payment type information, payment account information, and the mobile device identifier;
transmitting, by the configuration portal server, policy setting information and payment type information to a mobile wallet registry system;
receiving, by the configuration portal server, a wallet identifier from the mobile wallet registry system; and
storing, by the configuration portal server, the wallet identifier in the sponsor wallet.
20. The computer-implemented method of claim 19, wherein the wallet boarding request includes the payment type information and the payment account information.
21. The computer-implemented method of claim 19, wherein the payment account information includes information associated with more than one payment account.
22. The computer-implemented method of claim 19, wherein the policy setting information includes multiple policies, and wherein each of the multiple policies is associated with at least one payment account identified in the payment account information.
23. The computer-implemented method of claim 19, wherein the policy setting information includes at least one policy that defines how a payment account identified in the payment account information is allowed to be used, wherein the at least one policy includes a threshold amount or a category of merchant.
24. The computer-implemented method of claim 19, further comprising, in response to receiving a token generation request from a mobile device, transmitting, by the configuration portal server to the mobile wallet registry system, a token request.
25. The computer-implemented method of claim 24, further comprising, in response to receiving a token from the mobile wallet registry system, transmitting, by the configuration portal server, the token to the mobile device.
26. The computer-implemented method of claim 19, further comprising, in response to receiving a token generation request from a mobile device, transmitting, by the mobile wallet registry system, the token to the mobile device.
27. The computer-implemented method of claim 19, further comprising:
receiving, by the configuration portal server, a request for payment account information from the mobile wallet registry system, the request for payment account information including a wallet identifier; and
transmitting, by the configuration portal server to the mobile wallet registry system, payment account information associated with the wallet identifier.
28. A system for managing mobile tokens, the system comprising:
a mobile token data store configured to store token records, each token record including a mobile token and an associated wallet identifier;
a mobile token validation module communicatively coupled to the mobile token data store and configured to:
receive a validation request from a requestor, the validation request including a mobile token and a payment type indication;
retrieve a wallet identifier associated with the mobile token from a token record in the mobile token data store;
transmit the wallet identifier to a configuration portal server;
receive a validation response created by an issuer processor system of the configuration portal server; and
transmit the validation response to the requestor.
29. The system of claim 28, wherein the requestor is a payment gateway module;
30. The system of claim 28, wherein the requestor is a merchant point-of-sale device.
31. The system of claim 28, wherein the mobile token data store is configured to store a plurality of token records each including a different mobile token and a given associated wallet identifier.
32. The system of claim 28, further comprising a mobile token generation module configured to:
generate a token in response to a token request received from a configuration portal server, the token request including a wallet identifier; and
store a token record including the token and the wallet identifier in the mobile token data store.
33. The system of claim 32, wherein the mobile token generation module is further configured to transmit the token to the configuration portal server.
34. The system of claim 32, wherein the mobile token generation module is further configured to transmit the token to a mobile device.
35. The system of claim 28, further comprising a policy and fraud detection module configured to enforce wallet policies and detect fraud patterns.
36. The system of claim 35, wherein wallet policies include one or more of a spending limit per token, a token expiration date, a token window, allowable merchant categories, and token velocity.
37. The system of claim 35, wherein the mobile token data store is further configured to store wallet policies.
38. A mobile device configured to use a mobile wallet, wherein the mobile device is configured to execute:
one or more sponsor applications; and
a service application; wherein the service application is configured to:
receive a request from a sponsor application to use a payment token associated with a payment type;
verify that the sponsor application is authorized to use the requested payment type; and
in response to determining that the sponsor application is authorized, provide the requested payment token for use by the sponsor application.
39. The mobile device of claim 38, wherein providing the requested payment token for use by the sponsor application includes transmitting the payment token to a merchant point-of-sale device.
40. The mobile device of claim 39, wherein transmitting the payment token to a merchant point-of-sale device includes transmitting the payment token to a merchant point-of-sale device using a proximity payment technique.
41. The mobile device of claim 39, wherein the service application is further configured to receive transaction information from the merchant point-of-sale device.
42. The mobile device of claim 41, wherein the transaction information includes one or more of an electronic receipt; a balance notification; a coupon; detailed transaction data; a selection of a payment type; and a transaction denial.
43. The mobile device of claim 38, wherein the service application is further configured to:
transmit a request for a payment token;
receive the payment token; and
store the payment token for use by one or more sponsor applications.
44. The mobile device of claim 43, wherein the request for a payment token is transmitted to a mobile wallet registry system.
45. The mobile device of claim 43, wherein the request for a payment token is transmitted to a configuration portal server.