Event-triggered business-to-business electronic payment processing apparatuses, methods and systems

• US 9,760,871 B1
• Filed: 03/14/2013
• Issued: 09/12/2017
• Est. Priority Date: 04/01/2011
• Status: Active Grant

• Current Assignee: Visa International Service Association (Visa, Inc.)
• Original Assignee: Visa International Service Association (Visa, Inc.)
• Inventors: Pourfallah, Stacy, Subramanian, Kaushik
• Primary Examiner(s): Hamilton, Lalita M
• Application Number:
  US13/831,389
• Time in Patent Office: 1,643 Days
• Field of Search: 705 35, 705 40, 705 4, 705 39
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/14 specially adapted for billing systems
• CPC Class Codes: G06Q 20/223 based on the use of peer-to-peer networks
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/3274 using a pictured code, e.g. barcode or QR-code, being displayed on the M-device
• CPC Class Codes: G06Q 20/3276 using a pictured code, e.g. barcode or QR-code, being read by the M-device
• CPC Class Codes: G06Q 20/36 using electronic wallets or electronic money safes
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 20/4012 Verifying personal identification numbers [PIN]
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06V 10/17 using hand-held instruments
• CPC Class Codes: G06V 30/224 of printed characters having additional code marks or containing code marks

Abstract

The Event-Triggered Business-To-Business Electronic Payment Processing Apparatuses, Methods And Systems (hereinafter “B2B-PAY”) provides a business-to-business payment platform which facilitates business to business payment triggered by a user event, and transforms purchase item information inputs or purchase receipt inputs via B2B-PAY components into restricted-use account payment settlement outputs. In one embodiment, a method is disclosed, including: receiving a first payment request from a healthcare provider, the first payment request including healthcare bill information and user payment information loaded via a user vehicle; transmitting a second payment request to an insurance provider, the second payment request comprising an insured amount; receiving an indication of an approved amount from the insurance provider; facilitating payment of the approved amount from the insurance provider to the healthcare provider; calculating a user responsible amount; and facilitating payment of the calculated user responsible amount from the user to the healthcare provider.

Claims

1. A business-to-business transaction processing processor-implemented method, comprising:

obtaining, by a processor, a purchase payment request having a processor-executable link from a user triggering event indication, said user triggering event indication being received upon user instantiation of a web enabled mobile computing device at a B2B-Pay terminal of a first business entity, said user triggering event indication comprises a business-to-business payment event indication, said first business entity being different from the user, said web enabled mobile computing device providing user interface elements for the user to interact with user interface elements provided by the B2B-Pay terminal;

determining, by the processor, in response to executing the processor-executable link a second business entity sponsoring the purchase payment in response to parsing the purchase payment request, said second business entity being different from the first business entity and the user, said determining comprises receiving an instruction in response to a selection from the user for the second business entity on the web enabled mobile computing device;

obtaining, by the processor, purchase sponsoring instructions provided by the second business entity, said obtained purchase sponsoring instructions comprising verifying payment eligibility data of the user;

determining, by the processor, a payment sponsoring amount from the second business entity to the first business entity in response to the obtained purchase sponsoring instructions and the obtained purchase payment request;

generating, by the processor, a business-to-business financial transaction request for the second business entity to transfer the determined payment sponsoring amount to the first business entity;

initiating, by the processor, a business-to-business financial transaction between the second business entity to the first business entity in response to the received user triggering event indication by sending the generated business-to-business financial transaction request to the second business entity;

receiving, by the processor, a payment amount adjudication indication from the second business entity;

retrieving, by the processor, account details of a first bank account of the first business entity and a second bank account of the second business entity, said first bank account being different from the second bank account and being different from a user bank account of the user; and

transacting, by the processor, the adjudicated payment amount from the second bank account of the second business entity to the first bank account of the first business entity.

2. The method of claim 1, wherein the user triggering event comprises a user swiping a prepaid card at the first business entity.

3. The method of claim 1, wherein the user triggering event comprises a user instantiates a digital wallet at the first business entity.

4. The method of claim 1, wherein the first business entity is a healthcare provider.

5. The method of claim 1, wherein the second business entity is an insurance carrier.

6. The method of claim 1, wherein the second business entity is a government benefit administrator.

7. The method of claim 1, wherein the first business entity is a utility biller.

8. The method of claim 1, wherein the purchase payment request is formatted in compliance with a healthcare payment data format.

9. The method of claim 8, wherein the healthcare payment data format comprises National Council for Prescription Drug Programs (NCPDP).

10. The method of claim 1, wherein the payment sponsoring amount comprises an insured amount for the payment purchase.

11. The method of claim 1, wherein the adjudication indication comprises an insured amount adjustment from an insurance carrier.

12. The method of claim 1, wherein the purchase payment request comprises a virtual PAN number.

13. The method of claim 1, wherein the business-to-business financial transaction between the second business entity to the first business entity is initiated without latency to the user triggering event indication.

14. The method of claim 1, further comprising:

calculating a user responsible amount; and

facilitating payment of the calculated user responsible amount from the user to the first business entity.

15. The method of claim 1, further comprising:

obtaining a financial transaction record between the first business entity and the second business entity; and

obtaining a transacted payment amount transferred from the second business entity to the first business entity.

16. The method of claim 15, further comprising:

comparing the adjudicated payment amount with the obtained transacted insurance payment amount; and

generating a payment reconciliation report based on the comparison.

17. The method of claim 15, further comprising:

receiving a supplemental payment request from the first business entity when the payment reconciliation report indicates the obtained transacted payment amount is insufficient; and

transmitting the supplemental payment request to the second business entity.

18. A business-to-business transaction processing system, comprising:

means for receiving a user triggering event indication upon user instantiation of a web enabled mobile computing device at a B2B-Pay terminal of a first business entity, said user triggering event indication comprises a business-to-business payment event indication, said first business entity being different from the user, said web enabled mobile computing device providing user interface elements for the user to interact with user interface elements provided by the B2B-Pay terminal;

means for obtaining a purchase payment request from the received user triggering event indication;

means for determining a second business entity sponsoring the purchase payment by parsing the purchase payment request, said second business entity being different from the first business entity and the user, said determining comprises receiving an instruction in response to a selection from the user for the second business entity on the web enabled mobile computing device;

means for obtaining purchase sponsoring instructions provided by the second business entity, said obtained purchase sponsoring instructions comprising verifying payment eligibility data of the user;

means for determining a payment sponsoring amount from the second business entity to the first business entity in response to the obtained purchase sponsoring instructions and the obtained purchase payment request;

means for generating a business-to-business financial transaction request for the second business entity to transfer the determined payment sponsoring amount to the first business entity;

means for initiating a business-to-business financial transaction between the second business entity to the first business entity in response to the received user triggering event indication by sending the generated business-to-business financial transaction request to the second business entity;

means for receiving a payment amount adjudication indication from the second business entity;

means for retrieving account details of a first bank account of the first business entity and a second bank account of the second business entity, said first bank account being different from the second bank account and being different from a user bank account of the user; and

means for transacting the adjudicated payment amount from the second bank account of the second business entity to the first bank account of the first business entity.

19. A business-to-business transaction processing apparatus, comprising:

a memory;

a processor disposed in communication with said memory, and configured to issue a plurality of processing instructions stored in the memory, wherein the processor issues instructions to;

receive a user triggering event indication by a user upon user instantiation of a web enabled mobile computing device at a B2B-Pay terminal of a first business entity, said user triggering event indication comprises a business-to-business payment event indication, said first business entity being different from the user, said web enabled mobile computing device providing user interface elements for the user to interact with user interface elements provided by the B2B-Pay terminal;

obtain a purchase payment request from the received user triggering event indication;

determine a second business entity sponsoring the purchase payment by parsing the purchase payment request, said second business entity being different from the first business entity and the user, said determine comprises receive an instruction in response to a selection from the user for the second business entity on the web enabled mobile computing device;

obtain purchase sponsoring instructions provided by the second business entity, said obtained purchase sponsoring instructions comprising verifying payment eligibility data of the user;

determine a payment sponsoring amount from the second business entity to the first business entity in response to the obtained purchase sponsoring instructions and the obtained purchase payment request;

generate a business-to-business financial transaction request for the second business entity to transfer the determined payment sponsoring amount to the first business entity;

initiate a business-to-business financial transaction between the second business entity to the first business entity in response to the received user triggering event indication by sending the generated business-to-business financial transaction request to the second business entity;

receive a payment amount adjudication indication from the second business entity;

retrieve account details of a first bank account of the first business entity and a second bank account of the second business entity, said first bank account being different from the second bank account and being different from a user bank account of the user; and

transact the adjudicated payment amount from the second bank account of the second business entity to the first bank account of the first business entity.

20. A business-to-business transaction processing processor-readable non-transitory medium storing processor-executable instructions executable by a processor to:

receive a user triggering event indication upon user instantiation of a web enabled mobile computing device at a B2B-Pay terminal of a first business entity;

obtain, by the processor, a purchase payment request from the received user triggering event indication, said user triggering event indication being received upon user instantiation of the web enabled mobile computing device at the B2B-Pay terminal at the first business entity, said user triggering event indication comprises a business-to-business payment event indication, said first business entity being different from the user, said web enabled mobile computing device providing user interface elements for the user to interact with user interface elements provided by the B2B-Pay terminal;

determine, by the processor, a second business entity sponsoring the purchase payment by parsing the purchase payment request, said second business entity being different from the first business entity and the user, said determining comprises receiving an instruction in response to a selection from the user for the second business entity on the web enabled mobile computing device;

obtain, by the processor, purchase sponsoring instructions provided by the second business entity, said obtained purchase sponsoring instructions comprising verifying payment eligibility data of the user;

determine, by the processor, a payment sponsoring amount from the second business entity to the first business entity in response to the obtained purchase sponsoring instructions and the obtained purchase payment request;

generate, by the processor, a business-to-business financial transaction request for the second business entity to transfer the determined payment sponsoring amount to the first business entity;

initiate, by the processor, a business-to-business financial transaction between the second business entity to the first business entity in response to the received user triggering event indication by sending the generated business-to-business financial transaction request to the second business entity;

receive, by the processor, a payment amount adjudication indication from the second business entity;

retrieve, by the processor, account details of a first bank account of the first business entity and a second bank account of the second business entity, said first bank account being different from the second bank account and being different from a user bank account of the user; and

transact, by the processor, the adjudicated payment amount from the second bank account of the second business entity to the first bank account of the first business entity.