Multiple merchant payment processor platform apparatuses, methods and systems

• US 10,438,176 B2
• Filed: 03/31/2014
• Issued: 10/08/2019
• Est. Priority Date: 07/17/2011
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Johnson, Alan, Kumar, Ajay, Wang, John, Dutta, Rajiv
• Primary Examiner(s): Ebersman, Bruce I
• Assistant Examiner(s): Anderson, John A
• Application Number:
  US14/230,327
• Publication Number:
  US 20140249999A1
• Time in Patent Office: 2,017 Days
• Field of Search: 705 39
• CPC Class Codes: G06Q 20/027 involving a payment switch or gateway
• CPC Class Codes: G06Q 20/0855 involving a third party
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/34 using cards, e.g. integrated circuit [IC] cards or magnetic cards
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 30/0207 Discounts or incentives, e.g. coupons or rebates

Abstract

The MULTIPLE MERCHANT PAYMENT PROCESSOR PLATFORM APPARATUSES, METHODS AND SYSTEMS (“MID-PLATFORM”) enable merchants to customize the way payments made to them are processed. For example, a computer-implemented MID-Platform receives a payment request associated with a site (e.g., a website) and identifies a site profile associated with the site. The site profile is associated with one or more account processors and one or more transaction preference rules for selecting one of the account processors. The MID-Platform processes information associated with the payment request according to one or more transaction preference rules to select one of the account processors. Then, the MID-Platform sends a payment processing request to the selected account processor.

Claims

1. A computer-implemented multiple merchant payment processor method, comprising:

receiving, using one or more data processors, a payment request associated with a site of a merchant;

determining whether the payment request includes a previously assigned merchant identification (“

ID”

);

in response to the determining that the payment request includes the previously assigned merchant ID being positive, formulating a payment transaction authorization request in a HTTP(S) POST message based on the previously assigned merchant ID and the payment request;

transmitting the payment transaction authorization request via a payment network in a form of a HTTP(S) POST message for processing of the payment transaction authorization request;

in response to the determining that the payment request fails to include the previously assigned merchant ID being negative, generating, using the one or more data processors, one or more site-level profile profiles for the site of the merchant, each of the one or more site-level profile profiles being associated with a merchant identification (“

MID”

) of the site of the merchant, wherein the one or more site-level profiles are based on an identification key included in the payment request, wherein the one or more site-level profile profiles are associated with one account processor and one or more transaction preference rules for selecting the one account processor for processing the payment request, wherein the one or more data processors provide a graphical user interface (GUI) having user interface elements for modifying and configuring the one or more transaction preference rules for the one account processor, wherein the one or more data processors further, as part of the GUI;

send a payment checkout widget for the site of the merchant;

upon registration information from the merchant, generate an application programming interface (API) key and a shared secret key for the merchant, said API key and said shared secret key for invoking the payment checkout widget at the site of the merchant; and

associate the MID with each of the one or more site-level profile profiles;

processing, using the one or more data processors, information associated with the payment request according to one or more transaction preference rules to select the one account processor; and

sending, using the one or more data processors, a payment processing request based on the payment request to the selected one account processor, wherein the one or more data processors invoke a transaction UI based on the API key and the shared secret key in response to sending.

2. The method of claim 1, wherein the one or more site-level profile profiles are associated with a merchant profile.

3. The method of claim 2, wherein the merchant profile is associated with one or more site-level profiles.

4. The method of claim 2, wherein the merchant profile is managed by a merchant who transacts business on or at the site.

5. The method of claim 1, wherein the site is a website.

6. The method of claim 1, wherein the one or more site-level profile profiles are associated with one or more account processor profiles corresponding to the one or more account processors.

7. The method of claim 6, wherein one of the account processor profiles is associated with a subset of the one or more transaction preference rules.

8. The method of claim 1, wherein one of the one or more transaction preference rules is associated with transaction characteristics selected from the group including currency type, currency amount, geographic region, product category, and service category.

9. The method of claim 1, wherein one of the account processors is comprises a financial institution.

10. The method of claim 1, wherein the information associated with the payment request includes transaction information.

11. A computer-implemented multiple merchant payment processor system, comprising:

a memory;

one or more data processors disposed in communication with said memory, and configured to process a plurality of processing instructions stored in said memory, wherein the one or more data processors process instructions to;

receive receiving a payment request associated with a site of a merchant, determine determining whether the payment request includes a previously assigned merchant identification (“

ID”

);

in response to the determine determining that the payment request includes the previously assigned merchant ID being positive, formulate formulating a payment transaction authorization request in a HTTP(S) POST message based on the previously assigned merchant ID and the payment request;

transmit transmitting the payment transaction authorization request via a payment network in a form of a HTTP(S) POST message for processing of the payment transaction authorization request;

in response to the determine determining that the payment request fails to include the previously assigned merchant ID being negative, generate generating one or more site-level profile profiles for the site of the merchant, each of the one or more site-level profile profiles being associated with a merchant identification (“

MID”

) of the site of the merchant, wherein the one or more site-level profiles are based on an identification key included in the payment request, wherein the one or more site-level profile profiles are associated with one account processor and one or more transaction preference rules for selecting the one account processor for processing the payment request, wherein the one or more data processors provide a graphical user interface (GUI) having user interface elements for modifying and configuring the one or more transaction preference rules for the one account processor, wherein the one or more data processors further, as part of the GUI;

send sending a payment checkout widget for the site of the merchant;

upon registration information from the merchant, generate generating an application programming interface (API) key and a shared secret key for the merchant, said API key and said shared secret key for invoking the payment checkout widget at the site of the merchant; and

associate associating the MID with each of the one or more site-level profile profiles;

process processing information associated with the payment request according to one or more transaction preference rules to select the one account processor; and

send sending a payment processing request based on the payment request to the selected one account processor, wherein the one or more data processors invoke a transaction UI based on the API key and the shared secret key in response to sending.

12. The system of claim 11, wherein the one or more site-level profiles are associated with a merchant profile.

13. The system of claim 11, wherein the one or more site-level profiles are associated with one or more account processor profiles corresponding to the one account processor.

14. The system of claim 13, wherein one of the account processor profiles is associated with a subset of the one or more transaction preference rules.

15. The system of claim 11, wherein one of the one or more transaction preference rules is associated with transaction characteristics selected from the group including currency type, currency amount, geographic region, product category, and service category.

16. The system of claim 11, wherein the information associated with the payment request includes transaction information.

17. A non-transitory merchant payment processor-readable non-transitory medium storing instructions executable by a data processor to:

receive receiving a payment request associated with a site of a merchant,

determine determining whether the payment request includes a previously assigned merchant identification (“

ID”

);

in response to the determine determining that the payment request includes the previously assigned merchant ID being positive, formulate formulating a payment transaction authorization request in a HTTP(S) POST message based on the previously assigned merchant ID and the payment request;

transmit transmitting the payment transaction authorization request via a payment network in a HTTP(S) POST message for processing of the payment transaction authorization request;

in response to the determine determining that the payment request fails to include the previously assigned merchant ID being negative, generate generating one or more site-level profile profiles for the site of the merchant, each of the one or more site-level profile profiles being associated with a merchant identification (“

MID”

) of the site of the merchant, wherein the one or more site-level profiles are based on an identification key included in the payment request, wherein the one or more site-level profile profiles are associated with one account processors and one or more transaction preference rules for selecting the one account processor for processing the payment request, wherein the one or more data processors provide a graphical user interface (GUI) having user interface elements for modifying and configuring the one or more transaction preference rules for the one account processor, wherein the one or more data processors further, as part of the GUI;

send sending a payment checkout widget for the site of the merchant;

upon registration information from the merchant, generate generating an application programming interface (API) key and a shared secret key for the merchant, said API key and said shared secret key for invoking the payment checkout widget at the site of the merchant; and

associate associating the MID with each of the one or more site-level profile profiles;

process processing information associated with the payment request according to one or more transaction preference rules to select one of the account processors; and

invoke invoking a transaction UI based on the API key and the shared secret key to send a payment processing request to the selected account processor.

18. The processor readable medium of claim 17, wherein one of the one or more transaction preference rules is associated with transaction characteristics selected from the group including currency type, currency amount, geographic region, product category, and service category.

19. The processor readable medium of claim 17, wherein the one or more site-level profiles are associated with one or more account processor profiles corresponding to the one account processor.

20. The processor readable medium of claim 17, wherein one of the account processor profiles is associated with a subset of the one or more transaction preference rules.