Systems and Methods for Use in Processing Transactions to Payment Accounts

• US 20160364726A1
• Filed: 06/09/2015
• Published: 12/15/2016
• Est. Priority Date: 06/09/2015
• Status: Active Application

• Current Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Original Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Inventors: Lopez, Ariel, Espinoza, Csar, Zuluaga, Carlos
• Application Number:
  US14/734,706
• Publication Number:
  US 20160364726A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/227 characterised in that multiple accounts are available, e.g. to the payer
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules

Abstract

Systems and methods are provided for processing transactions made at various merchants to payment accounts issued by other different merchants. One exemplary method generally includes receiving a charge request from a first merchant, relating to a transaction for a product at the first merchant between the first merchant and a consumer, where the charge request includes an identifier associated with a payment account used by the consumer in the transaction and issued by a second merchant. The method also generally includes determining, at a computing device, based on the identifier, a uniform account number (UAN) for the payment account where the UAN is unique to the payment account and defining a format different than a format of the identifier, and then causing, based on the determined UAN, a balance of the payment account to be altered.

Claims

1. A computer-implemented method for use in processing at least one transaction, between a consumer and a first merchant, to a payment account issued by a second merchant, the method comprising:

receiving a charge request for a product from the first merchant, the charge request including an identifier associated with the payment account issued by the second merchant;

determining, at a computing device, based on the identifier, a uniform account number (UAN) for the payment account, the UAN being unique to the payment account and defining a format different than a format of the identifier; and

causing, based on the determined UAN, a balance of the payment account to be altered.

2. The method of claim 1, wherein determining the UAN based on the identifier includes calculating at least part of the UAN based on the identifier.

3. The method of claim 1, wherein determining the UAN based on the identifier includes retrieving at least part of the UAN from memory, based on the identifier.

4. The method of claim 1, wherein a format of the identifier includes from 8 to 15 hexadecimal or decimal digits;

and/or

wherein a format of the UAN includes at least 10 hexadecimal or decimal digits.

5. The method of claim 1, wherein causing the balance to be altered includes:

identifying an amount indicated in the charge request;

identifying the payment account associated with the UAN; and

debiting the amount from the payment account.

6. The method of claim 1, wherein causing the balance to be altered includes transmitting the charge request to the second merchant.

7. The method of claim 1, wherein the first merchant and the second merchant are the same merchant.

8. The method of claim 1, wherein causing the balance to be altered includes causing the balance to be altered by one of:

an amount of the at least one transaction and a pre-authorization amount associated with the at least one transaction.

9. The method of claim 1, further comprising transmitting a balance summary to the second merchant, at one of a predetermined time and upon request from the second merchant.

10. A system for processing at least one transaction, between a consumer and a first merchant, to a payment account issued by a second merchant, the system comprising:

a payment network including a memory and configured to;

receive a charge request for a transaction to a payment account issued by a first merchant, the charge request including an identifier of the payment account and a charge amount;

in response to the charge request, calculate at least part of a UAN, based on the identifier; and

debit the charge amount from the payment account associated with the UAN.

11. The system of claim 10, wherein the payment network, in order to calculate at least a part of the UAN, is configure to:

calculate a serial number of the UAN based on a consumer identifier/ID included in the identifier; and

calculate a MIN of the UAN based on a merchant identifier/ID for the first merchant included in the identifier.

12. The system of claim 10, wherein the payment network is configured to assign at least a different part of the UAN to be consistent with a prior-assigned UAN for a payment account, the prior-assigned UAN included in a memory and associated with the second merchant.

13. The system of claim 10, wherein the payment network includes a database in the memory, the databased including multiple UANs each associated with a different merchant payment account;

and

wherein the payment network is configured to retrieve the UAN from the database, based on the identifier included in the charge request.

14. The system of claim 10, further comprising the first merchant and a POS device associated with a first merchant;

and

wherein the payment network is configured to receive the charge request from the POS device associated with the first merchant and report a balance associated with the payment account to the second merchant.

15. The system of claim 14, wherein the first merchant is a toll operator and the POS device is configured to read toll tags associated with vehicles in the vicinity of at least one of a bridge and a road associated with the toll operator;

and

wherein the second merchant is a toll operator different than the first merchant.

16. A non-transitory computer readable storage media including executable instructions which, when executed by at least one processor, cause the at least one processor to:

receive a charge request for a transaction, the request including an identifier associated with a merchant payment account;

determine, based on the identifier, a uniform account number (UAN), the UAN being unique to the merchant payment account; and

alter a balance associated with the merchant payment account based on the charge request and the UAN.

17. The non-transitory computer readable storage media of claim 16, wherein the executable instructions, when executed by the at least one processor, cause the at least one processor to retrieve the UAN when the UAN is assigned with the identifier;

and

wherein the executable instructions, when executed by the at least one processor, further cause the at least one processor to assign the UAN, based on the identifier, when no UAN is assigned to the identifier.

18. The non-transitory computer readable storage media of claim 17, wherein the executable instructions, when executed by the at least one processor, cause the at least one processor to calculate at least a MIN and a serial number of the UAN based on the identifier, in order to determine the UAN;

and

wherein the MIN is unique to a first merchant, the first merchant being an issuer of the payment account.

19. The non-transitory computer readable storage media of claim 16, wherein the executable instructions, when executed by the at least one processor, cause the at least one processor to alter the balance associated with the merchant payment account when said account is managed by a service provider;

and

wherein the executable instructions, when executed by the at least one processor, further cause the at least one processor to transmit a charge request and/or the UAN to an issuing merchant for the merchant payment account.