US 12,271,902 B2
Non-native account processing
Vikram Modi, Lafayette, CA (US); Sunil Joshi, Santa Clara, CA (US); and Shantnu Singh, Foster City, CA (US)
Assigned to Visa International Service Association, San Francisco, CA (US)
Appl. No. 17/631,796
Filed by Visa International Service Association, San Francisco, CA (US)
PCT Filed Aug. 3, 2020, PCT No. PCT/US2020/044776
§ 371(c)(1), (2) Date Jan. 31, 2022,
PCT Pub. No. WO2021/026086, PCT Pub. Date Feb. 11, 2021.
Claims priority of provisional application 62/882,377, filed on Aug. 2, 2019.
Prior Publication US 2022/0270095 A1, Aug. 25, 2022
Int. Cl. G06Q 20/40 (2012.01); G06Q 20/10 (2012.01); G06Q 20/38 (2012.01)
CPC G06Q 20/4014 (2013.01) [G06Q 20/102 (2013.01); G06Q 20/382 (2013.01); G06Q 20/405 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method for conducting a transaction with a non-native account, the method comprising:
receiving an account identifier scheme that is used by a third-party entity to provide access to accounts associated with the third-party entity,
wherein the third-party entity is a mobile wallet service provider;
assigning an entity identifier to the third-party entity based on the account identifier scheme that is used by the third-party entity,
wherein the entity identifier that is assigned to the third-party entity conforms to a native format used by a processing system;
modifying an application programming interface (API) to recognize account identifiers of the third-party entity by inserting code into the API to parse parameters sent with an API call to determine a target account of the transaction and the third-party entity associated with the target account,
wherein, based on the modifying, recognizing, by the application programming interface the account identifiers of payment accounts of the third-party entity,
wherein the inserted code is configured to verify that the account identifiers adhere to the account identifier scheme used by the third-party entity;
receiving a transaction request to execute the transaction, the transaction request including a resource provider identifier of the third-party entity and an account identifier of an account of the third-party entity,
wherein the resource provider identifier of the third-party entity identifies a name of a resource provider;
determining, using the modified application programming interface, the entity identifier assigned to the third-party entity; and
processing the transaction using the entity identifier assigned to the third-party entity.