US20170364890A1 - System and method of payment of merchants on behalf of payment card system transaction acquirers - Google Patents

System and method of payment of merchants on behalf of payment card system transaction acquirers Download PDF

Info

Publication number
US20170364890A1
US20170364890A1 US15/621,327 US201715621327A US2017364890A1 US 20170364890 A1 US20170364890 A1 US 20170364890A1 US 201715621327 A US201715621327 A US 201715621327A US 2017364890 A1 US2017364890 A1 US 2017364890A1
Authority
US
United States
Prior art keywords
merchant
account
payment
transaction
card
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
US15/621,327
Inventor
Sandeep Malhotra
Shanthan Subramaniam
Dana Lorberg
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mastercard International Inc
Original Assignee
Mastercard International Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US201662350322P priority Critical
Priority to US201662350407P priority
Priority to US201662350335P priority
Priority to US201662350416P priority
Priority to US201662350831P priority
Priority to US201662351164P priority
Priority to US201662351227P priority
Priority to US201662350821P priority
Priority to US201662351016P priority
Priority to US201662351155P priority
Application filed by Mastercard International Inc filed Critical Mastercard International Inc
Priority to US15/621,327 priority patent/US20170364890A1/en
Assigned to MASTERCARD INTERNATIONAL INCORPORATED reassignment MASTERCARD INTERNATIONAL INCORPORATED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LORBERG, DANA J, MALHOTRA, SANDEEP, SUBRAMANIAM, Shanthan
Publication of US20170364890A1 publication Critical patent/US20170364890A1/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • G06Q20/204—Point-of-sale [POS] network systems comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
    • G06N20/00—Machine learning
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G06Q20/023—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] the neutral party being a clearing house
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G06Q20/027—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] involving a payment switch or gateway
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/102—Bill distribution or payments
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/105—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems involving programming of a portable memory device, e.g. IC cards, "electronic purses"
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/108—Remote banking, e.g. home banking
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • G06Q20/202—Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3221—Access to banking information through M-devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/325—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/341—Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/385—Payment protocols; Details thereof using an alias or single-use codes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/387—Payment using discounts or coupons
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4012—Verifying personal identification numbers [PIN]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4016—Transaction verification involving fraud or risk level assessment in transaction processing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/405—Establishing or using transaction specific rules
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation, credit approval, mortgages, home banking or on-line banking
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING; COUNTING
    • G06Q—DATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation, e.g. computer aided management of electronic mail or groupware; Time management, e.g. calendars, reminders, meetings or time accounting
    • G06Q10/107—Computer aided management of electronic mail

Abstract

A card payment network handles a payment card account system transaction. The transaction involves a merchant and was acquired by a transaction acquirer. The card payment network initiates an electronic funds transfer to credit the merchant's bank deposit account on behalf of the transaction acquirer.

Description

    CROSS REFERENCE TO RELATED APPLICATIONS
  • This application claims the benefit of U.S. Provisional Patent Application Nos. 62/350,322 (filed on Jun. 15, 2016); 62/350,335 (filed Jun. 15, 2016); 62/350,407 (filed Jun. 15, 2016); 62/351,155 (filed Jun. 16, 2016); 62/350,821 (filed Jun. 16, 2016); 62/351,016 (filed Jun. 16, 2016); 62/351,227 (filed Jun. 16, 2016); 62/350,831 (filed Jun. 16, 2016); 62/350,416 (filed Jun. 15, 2016); and 62/351,164 (filed Jun. 16, 2016); the contents of which provisional applications are hereby incorporated by reference for all purposes.
    • BACKGROUND
  • In the “four party model” upon which most payment card systems are based, merchants that accept payment card transactions do so via agreements with transaction acquirers. Transaction acquirers are typically financial institutions authorized to act as intermediaries between merchants and the financial institutions that issue payment cards. Among the systems that employ the four party model are MasterCard, Visa, RuPay and Union Pay. Acquirers typically make payments to merchants using conventional EFT payment network rails and deposit funds to merchants' bank accounts based on the net settlement positions that the merchants have with the acquirer after netting fees and the applicable merchant discount rate (MDR). Set up of such payments is complex, and it is common for merchants to receive payment three days after a payment card transaction occurs.
  • The present inventors have now recognized opportunities to improve handling of payments to merchants with respect to payment card transactions.
    • BRIEF DESCRIPTION OF THE DRAWINGS
  • Features and advantages of some embodiments of the present disclosure, and the manner in which the same are accomplished, will become more readily apparent upon consideration of the following detailed description of the invention taken in conjunction with the accompanying drawings, which illustrate preferred and example embodiments and which are not necessarily drawn to scale, wherein:
  • FIG. 1 is a block diagram of a payment card account system.
  • FIG. 2 is block diagram of a payment system such as an EFT (electronic funds transfer) system.
  • FIG. 3 is a block diagram of a payment card system provided in accordance with aspects of the present disclosure.
  • FIG. 4 is a block diagram of an example computer system that may perform functions in the system of FIG. 3.
  • FIGS. 5, 6, 7 and 8 are flow charts that illustrate processes that may be performed in the system of FIG. 3 in accordance with aspects of the present disclosure.
    •  DESCRIPTION
  • In general, and for the purpose of introducing concepts of embodiments of the present disclosure, an EFT payment network in conjunction with a payment card system may be enabled to provide an integrated merchant payment solution for acquirers. The card system operator may provide an automated payment function that allows automated calculation of settlements due to merchants and immediate implementation of crediting or debiting the merchant's bank account using the EFT payment network.
  • Merchants may be enrolled in the automated system, from the acquirer's point of view, via bulk data loads to the payment card system operator. In addition or alternatively, the payment card system operator may host a self-serve portal that allows merchants to provide or update their bank account details. The automated system may also implement back office automation that executes payments when due based on triggers defined by the acquirer.
  • Such an automated system for paying merchants may shorten the time between execution of the card transaction and payment to merchant, thus improving the cash flows for merchants. Moreover, administrative burdens on acquirers may be reduced and acquirers may be enabled to provide better service to the merchants they support.
  • FIG. 1 is a block diagram that illustrates a payment card account system 100.
  • The system 100 includes a customer device 102 such as a magnetic stripe card, a payment IC (integrated circuit) card (contactless and/or contact), or a payment-enabled mobile device. Block 104 in FIG. 1 represents a merchant device such as a POS (point of sale) terminal/card reader. The merchant device 104 may also be considered part of the payment card account system 100. The customer device 102 may be presented to the merchant device 104, to consummate a purchase transaction and to permit the merchant device 104 to read payment card account data (including, e.g., a payment account number) from the customer device 102. In other situations, the merchant device 104 may be an e-commerce server computer, and the customer device 102 may be a personal computer, a mobile device running a mobile browser, etc.; in such situations, the customer device 102 may engage in an online shopping session with an e-commerce website hosted by the merchant device 104.
  • A computer 106 operated by an acquirer (acquiring financial institution) is also shown as part of the system 100 in FIG. 1. The acquirer computer 106 may receive a payment account system authorization request message for the transaction from the merchant device 104. The acquirer computer 106 may route the authorization request message via a card network 108 to a server computer 110 operated by the issuer of a payment account that is associated with the account number obtained by the merchant device 104 (e.g., from the customer device 102) and included in the authorization request message. The authorization response message generated by the payment issuer server computer 110 may be routed back to the merchant device 104 via the card network 108 and the acquirer computer 106.
  • One well known example of a card network is referred to as the “Banknet” system, and is operated by Mastercard International Incorporated, which is the assignee hereof.
  • The payment account issuer server computer 110 may be operated by or on behalf of a financial institution (“FI”) that issues payment accounts to individual users such as the customer who presented or operated the customer device 102 referred to above. For example, the payment card issuer server computer 110 may perform such functions as (a) receiving and responding to requests for authorization of payment account transactions to be charged to payment accounts issued by the FI; and (b) tracking and storing transactions and maintaining account records.
  • The payment card account system communications among the merchants, acquirers, card network and/or issuers may conform to a known standard such as ISO 8583.
  • The components of the system 100 as depicted in FIG. 1 are only those that are needed for processing a single transaction. A typical payment system may process many purchase transactions (including simultaneous transactions) and may include a considerable number of payment account issuers and their computers, a considerable number of acquirers and their computers, and numerous merchants and their devices, as well as a very large number of customer devices.
  • FIG. 2 is a block diagram that illustrates a payment network system 200, of which one example is the ACH (automated clearing house) system operated in the United States.
  • The system 200 includes an originator device 202, which may be a computer operated by an originator of a transaction. Common kinds of transactions are credit transactions and debit transactions. The originator is the party that initiates the transaction. The originator may be, for example, an individual or a corporation or other organization.
  • The system 200 further includes an originator PSP (payment services provider) computer 204. The originator PSP computer 204 receives payment instructions from the originator and forwards data entries that reflect the instructions to a payment system switch/network 206, which is also part of the system 200. The originator PSP computer 204 may be operated by an originator PSP of which the originator is a customer. The switch/network 206 may be operated by a governmental or private entity that serves as a clearing facility for the system 200.
  • Also included in the system 200 is a beneficiary PSP computer 208. The beneficiary PSP computer 208 receives entries from the payment system switch/network 206 and posts entries to accounts of depositors.
  • Still further, the system 200 includes a beneficiary 210 that is one of the depositors of the beneficiary PSP. In the case of a credit transaction, the account at the beneficiary PSP of the beneficiary may be credited with the amount instructed to be paid by the originator device 202. The beneficiary may be, for example, an individual or a corporation or other organization. Both PSPs may typically be banks or other financial institutions (FIs).
  • The communications among the parties in the system 200 may typically be conducted using XML (eXtensible Markup Language) and may comply with a standard according to ISO 20022.
  • The components of the system 200 as depicted in FIG. 2 are only those that are needed for processing a single transaction. A typical payment network system may process many transactions (including simultaneous transactions) and may include a considerable number of PSPs and their computers, one or more clearing operators, and numerous originators and beneficiaries
  • FIG. 3 is a block diagram of a payment card system 300 provided in accordance with aspects of the present disclosure.
  • The payment card system 300 may include all the components described above in connection with FIG. 1, including a customer device 102, a merchant device or system (labeled with reference numeral 104 a to reflect additional functionality it may provide in the system 300), a transaction acquirer (labeled with reference numeral 106 a to reflect additional functionality it may provide in the system 300), a card network (labeled with reference numeral 108 a to reflect additional functionality it may provide in the system 300), and a payment card issuer 110.
  • Further, the payment card system 300 may include a merchant payment services computer 302. The merchant payment services computer 302 may be in communication with the card network 108 a, and may be under common operation with the card network 108 a. In some embodiments, hardware making up the merchant payment services computer 302 may at least partially overlap with one or more computer systems that implement the card network 108 a. Details of the merchant payment services computer 302 will be described below. In general, the merchant payment services computer 302 may receive and store merchants' deposit account details, and may manage execution of payments due from acquirers to merchants. For embodiments in which the merchant payment services computer 302 is under common operation with the card network 108 a, or at least partially overlaps therewith in hardware terms, actions ascribed herein to the merchant payment services computer 302 may also be deemed to have been performed by the card network 108 a.
  • The payment card system 300 is further shown as incorporating an originator payment services provider (O-PSP) 304. The O-PSP may resemble item 204 described above in connection with FIG. 2 and may be in communication with the merchant payment services computer 302.
  • In addition, the payment card system 300 may include or be in a cooperative relationship with a payment switch/network 306, which may resemble item 206 described above in connection with FIG. 2. The payment switch/network 306 may be in communication with the O-PSP 304.
  • Still further, the payment card system 300 is shown as incorporating a beneficiary payment services provider (B-PSP) 308. The B-PSP 308 may resemble item 208 described above in connection with FIG. 2. The B-PSP 308 may be in communication with the payment switch/network 306.
  • Communication channels or possible communication channels are also shown from the acquirer 106 a and the merchant system 104 a, respectively, to the merchant payment services computer 302.
  • The components 304, 306, 308 shown in FIG. 3 may be part of an EFT system such as an ACH system.
  • Any one or more of the blocks shown in FIG. 3, in addition to representing the indicated entity, may also be considered to represent one or more computer systems operated by such entity.
  • FIG. 4 is a block diagram of an example embodiment of the merchant payment services computer 302.
  • Referring now to FIG. 4, the merchant payment services computer 302 may, in its hardware aspects, resemble a typical server computer and/or mainframe computer, but may be controlled by software to cause it to function as described herein.
  • The merchant payment services computer 302 may include a computer processor 400 operatively coupled to a communication device 401, a storage device 404, an input device 406 and an output device 408. The communication device 401, the storage device 404, the input device 406 and the output device 408 may all be in communication with the processor 400.
  • The computer processor 400 may be constituted by one or more processors. Processor 400 operates to execute processor-executable steps, contained in program instructions described below, so as to control the merchant payment services computer 302 to provide desired functionality.
  • Communication device 401 may be used to facilitate communication with, for example, other devices (such as other components of the payment system 300, including the card network 108 a, the O-PSP 308, the acquirer 106 a and/or the merchant system 104 a).
  • Communication device 401 may comprise numerous communication ports (not separately shown), to allow the merchant payment services computer 302 to communicate simultaneously with a number of other computers and other devices, including communications as required to simultaneously handle numerous interactions with other devices.
  • Input device 406 may comprise one or more of any type of peripheral device typically used to input data into a computer. For example, the input device 406 may include a keyboard and a mouse. Output device 408 may comprise, for example, a display and/or a printer.
  • Storage device 404 may comprise any appropriate information storage device, including combinations of magnetic storage devices (e.g., hard disk drives), optical storage devices such as CDs and/or DVDs, and/or semiconductor memory devices such as Random Access Memory (RAM) devices and Read Only Memory (ROM) devices, as well as so-called flash memory. Any one or more of such information storage devices may be considered to be a computer-readable storage medium or a computer usable medium or a memory.
  • Storage device 404 stores one or more programs for controlling processor 400. The programs comprise program instructions (which may be referred to as computer readable program code means) that contain processor-executable process steps of the merchant payment services computer 302, executed by the processor 400 to cause the merchant payment services computer 302 to function as described herein.
  • The programs may include one or more conventional operating systems (not shown) that control the processor 400 so as to manage and coordinate activities and sharing of resources in the merchant payment services computer 302, and to serve as a host for application programs (described below) that run on the merchant payment services computer 302.
  • The programs stored in the storage device 404 may include, for example, an application program 410 for providing one or more software interfaces to allow the merchant payment services computer 302 to receive input that provides details of merchant bank accounts.
  • Another program that may be stored in the storage device 404 is a web hosting application program 412 for enabling the merchant payment services computer 302 to host one or more web portals that are accessible by merchants and/or acquirers to allow them to enter or update merchant bank account details.
  • The storage device 404 may also store an application program 414 that programs the processor 400 to enable the merchant payment services computer 302 to manage payments to merchants on behalf of transaction acquirers. Details of the merchant payment application program 414 will be described below.
  • The storage device 404 may further store one or more software modules (block 416) that serve as software interfaces between the merchant payment services computer 302 and one or more O-PSPs that are constituents of the above discussed EFT system.
  • The storage device 404 may also store, and the merchant payment services computer 302 may also execute, other programs, which are not shown. For example, such programs may include communications software and a reporting application. The latter program may respond to requests from system administrators for reports on the activities performed by the merchant payment services computer 302. The other programs may also include, e.g., device drivers, database management software, etc.
  • Still further, the storage device 404 may store a database 418 that stores merchant bank account details that have been uploaded to the merchant payment services computer 302. The storage device 404 may also store one or more other databases 420 needed for operation of the merchant payment services computer 302.
  • Other computerized components of the system 300 may be constituted by computer hardware having the same type of components and hardware architecture as described herein with reference to FIG. 4.
  • FIG. 5 is a flow chart that illustrates a process that may be performed in the system of FIG. 3 in accordance with aspects of the present disclosure.
  • At 502 in FIG. 5, the merchant payment services computer 302 receives the merchant bank account details. In some embodiments, there may be three or more ways in which the merchant bank account details are received by the merchant payment services computer 302. These may include, for example: (a) the acquirer sending to the merchant payment services computer 302 a batch file containing merchant bank account details for a number of merchants supported by the acquirer; (b) uploading of merchant bank account detail by the acquirer to the merchant payment services computer 302 via a direct API; (c) merchant interaction with a merchant self-serve portal, as referred to above; and (d) one or more portals available for use by acquirer support personnel. Such portals may be made available by one or more of (i) a web service API that interacts with the acquiring system; (ii) a web portal for access by customer support staff from the acquirer's perspective; and (iii) a portal hosted by the merchant payment services computer 302 for access by merchants. The latter portal may serve as a “one stop shop” to allow the merchants to access acquiring services such that the merchants may make relevant changes to their payment bank account details and to access reports providing payment schedules and payment history for a given merchant's records.
  • The latter portal may also provide merchant registration by merchants directly and also access to acquirer support staff to enter details. FIG. 6 is a flow chart that illustrates an embodiment of such a process. At 602 in FIG. 6, the merchant/merchant staff member may enter the necessary data to identify the merchant and the merchant's bank account information. At 604 in FIG. 6, communication may occur between the merchant payment services computer 302 and the merchant/merchant staff member to satisfy “know your customer” compliance requirements. This may involve submission of suitable documentation (e.g., scanned facsimiles of documents) by the merchant and review of the same by system employees.
  • At 606 in FIG. 6, the merchant payment services computer 302 may engage in suitable ID&V (identification and verification) processes to assure authentication of the merchant engaging in the registration. (A similar ID&V process may occur when the merchant updates its registration data.)
  • At 608, the merchant payment services computer 302 may confirm to the merchant that the registration process is complete.
  • When the merchant-related data is uploaded by the acquirers, the uploaded data may include such relevant information as bank account details (bank, routing number and bank account number), MDR, service fees, and frequency of payments.
  • Referring again to FIG. 5, at 504, the merchant payment services computer 302 stores the merchant bank account details and other data uploaded by the acquirers and/or merchants.
  • As indicated at 506, further processing may occur at a later time after the merchant bank account details are received and stored by the merchant payment services computer 302. At the later time, the merchant payment services computer 302 may manage payments to merchants (block 508, FIG. 5) in regard to payment card account transactions involving the merchants. In doing so, the payments may be based on information collected by and made available from the card network 108 a (FIG. 3). The card network 108 a may have all the transaction details from the merchants and the acquirers and thus may enable the merchant payment services computer 302 to be informed of the merchants' net positions and to make payments accordingly directly to the merchants on behalf of the acquirers.
  • FIG. 7 is a flow chart that illustrates details of the processing that may occur at 506.
  • At 702 in FIG. 7, the merchant payment services computer 302 may receive card account transaction information for the merchant over a period of time (say, one day).
  • At 704, the merchant payment services computer 302 may apply the “MDR” (merchant discount rate) that is in effect between the merchant and the merchant's acquiring financial institution.
  • At 706, the merchant payment services computer 302 may calculate the merchant's net position vis a vis the acquirer, taking the MDR and any current charge-back transactions into account.
  • At 708, the merchant payment services computer 302 may initiate an EFT transaction to transfer—to the merchant—the merchant's net balance owed from the acquirer. This transaction may be a credit push payment via an EFT system, as represented by blocks 304, 306 and 308 in FIG. 3.
  • In various embodiments, or various situations, for a given merchant, the EFT transaction referred to at 708 may occur daily, or at regular times more frequently than daily, or in response to each payment card account system transaction that is accepted by the merchant and authorized by the account issuer, or each time a threshold balance due to the merchant is reached, or less frequently than daily; or some combination of the foregoing.
  • In some embodiments, the merchant payment services computer 302 may keep a running total of the amount due to the merchant from the acquirer. In cases where the funds transfer to the merchant is triggered by reaching a positive balance threshold, the acquirer may have set the threshold in accordance with its service agreement with the merchant and as part of the merchant registration performed by the acquirer.
  • In situations where the merchant is the debtor, then the merchant may be provided an opportunity through the merchant self-serve portal to initiate a push payment transaction to the acquirer to settle the merchant's obligation to the acquirer. FIG. 8 is a flow chart that illustrates a process whereby a merchant settles an obligation to the acquirer.
  • At decision block 802 in FIG. 8, the merchant payment services computer 302 determines whether the merchant's net position is such that the merchant owes money to the acquirer. If a positive determination is made at decision block 802, then block 804 may follow decision block 802. (In the absence of a positive determination at decision block 802, the process of FIG. 8 may end.) At block 804, the merchant payment services computer 302 may send a message such as a text message or an email message to the merchant to advise the merchant that the merchant has a negative balance vis a vis the acquirer.
  • A decision block 806 may follow block 804. At decision block 806, the merchant payment services computer 302 may determine whether the merchant has requested that a transfer occur to settle the merchant's obligation to the acquirer. If so, then block 808 may follow decision block 806. (In the absence of a positive determination at decision block 806, the process of FIG. 8 may end.) At 808, the merchant payment services computer 302 may initiate an EFT transfer charged to the merchant's account and to benefit the acquirer in order to settle the merchant's obligation.
  • An arrangement as described with reference to FIGS. 3-8 may simplify management of merchants by acquirers and at the same time may provide merchants with quick access to cash at their bank deposit accounts in respect to payment card account system transactions accepted by the merchant.
  • As used herein and in the appended claims, the term “computer” should be understood to encompass a single computer or two or more computers in communication with each other.
  • As used herein and in the appended claims, the term “processor” should be understood to encompass a single processor or two or more processors in communication with each other.
  • As used herein and in the appended claims, the term “memory” should be understood to encompass a single memory or storage device or two or more memories or storage devices.
  • As used herein and in the appended claims, a “server” includes a computer device or system that responds to numerous requests for service from other devices.
  • The above descriptions and illustrations of processes herein should not be considered to imply a fixed order for performing the process steps. Rather, the process steps may be performed in any order that is practicable, including simultaneous performance of at least some steps.
  • As used herein and in the appended claims, the term “payment card system account” includes a credit card account, a deposit account that the account holder may access using a debit card, a prepaid card account, or any other type of account from which payment transactions may be consummated. The terms “payment card system account” and “payment card account” and “payment account” are used interchangeably herein. The term “payment card account number” includes a number that identifies a payment card system account or a number carried by a payment card, or a number that is used to route a transaction in a payment system that handles payment card transactions. The term “payment card” includes a credit card, debit card, prepaid card, or other type of payment instrument, whether an actual physical card, electronic, or virtual.
  • As used herein and in the appended claims, the term “payment card system” or “payment account system” refers to a system for handling purchase transactions and related transactions. An example of such a system is the one operated by MasterCard International Incorporated, the assignee of the present disclosure. In some embodiments, the term “payment card system” may be limited to systems in which member financial institutions issue payment card accounts to individuals, businesses and/or other organizations.
  • Although the present invention has been described in connection with specific example embodiments, it should be understood that various changes, substitutions, and alterations apparent to those skilled in the art can be made to the disclosed embodiments without departing from the spirit and scope of the invention as set forth in the appended claims.

Claims (20)

What is claimed is:
1. A method comprising:
handling a payment card account system transaction in a card payment network, the transaction involving a merchant and having been acquired by a transaction acquirer; and
initiating an electronic funds transfer by the card payment network to credit the merchant's deposit account on behalf of the transaction acquirer.
2. The method of claim 1, wherein the electronic funds transfer is via an EFT (electronic funds transfer) system.
3. The method of claim 2, wherein the electronic funds transfer is via an ACH (automated clearing house) system.
4. The method of claim 1, wherein the electronic funds transfer effects a transfer of funds to said merchant's deposit account from an account belonging to said transaction acquirer.
5. The method of claim 1, wherein said electronic funds transfer executes a transfer of funds relating to a plurality of payment card account system transactions that includes said payment card account system transaction.
6. The method of claim 5, wherein said electronic funds transfer executes a transfer of funds relative to a net position of funds due to the merchant from the transaction acquirer.
7. The method of claim 6, wherein said net position is net of fees due to the transaction acquirer.
8. A method comprising:
handling a plurality of payment card account system transactions in a card payment network, the transactions all involving a merchant and having been acquired by a transaction acquirer; and
initiating an electronic funds transfer by the card payment network to credit the merchant's deposit account on behalf of the transaction acquirer, said funds transfer for transferring a net funds position from the transaction acquirer to the merchant in regard to said plurality of transactions.
9. The method of claim 8, wherein the electronic funds transfer is via an EFT (electronic funds transfer) system.
10. The method of claim 9, wherein the electronic funds transfer is via an ACH (automated clearing house) system.
11. The method of claim 8, wherein the electronic funds transfer effects a transfer of funds to said merchant's deposit account from an account belonging to said transaction acquirer.
12. The method of claim 8, wherein said net funds position is net of charge-back transactions and fees due to the transaction acquirer.
13. The method of claim 8, further comprising:
receiving, from the transaction acquirer, an account identifier that identifies said merchant's deposit account.
14. The method of claim 13, wherein:
said account identifier is received in a message, said message also including a discount rate that defines fees due to the transaction acquirer from the merchant.
15. An apparatus comprising:
a processor; and
a memory in communication with the processor, the memory storing program instructions, the processor operative with the program instructions to perform functions as follows:
handling a plurality of payment card account system transactions in a card payment network, the transactions all involving a merchant and having been acquired by a transaction acquirer; and
initiating an electronic funds transfer by the card payment network to credit the merchant's deposit account on behalf of the transaction acquirer, said funds transfer for transferring a net funds position from the transaction acquirer to the merchant in regard to said plurality of transactions.
16. The apparatus of claim 15, wherein the electronic funds transfer is via an EFT (electronic funds transfer) system.
17. The apparatus of claim 16, wherein the electronic funds transfer is via an ACH (automated clearing house) system.
18. The apparatus of claim 15, wherein the electronic funds transfer effects a transfer of funds to said merchant's deposit account from an account belonging to said transaction acquirer.
19. The apparatus of claim 15, wherein said net funds position is net of charge-back transactions and fees due to the transaction acquirer.
20. The apparatus of claim 15, wherein the processor is further operative with the program instructions to receive, from the transaction acquirer, an account identifier that identifies said merchant's deposit account, said account identifier received in a message, said message also including a discount rate that defines fees due to the transaction acquirer from the merchant.
US15/621,327 2016-06-15 2017-06-13 System and method of payment of merchants on behalf of payment card system transaction acquirers Pending US20170364890A1 (en)

Priority Applications (11)

Application Number Priority Date Filing Date Title
US201662350322P true 2016-06-15 2016-06-15
US201662350407P true 2016-06-15 2016-06-15
US201662350335P true 2016-06-15 2016-06-15
US201662350416P true 2016-06-15 2016-06-15
US201662351164P true 2016-06-16 2016-06-16
US201662351227P true 2016-06-16 2016-06-16
US201662350821P true 2016-06-16 2016-06-16
US201662351016P true 2016-06-16 2016-06-16
US201662351155P true 2016-06-16 2016-06-16
US201662350831P true 2016-06-16 2016-06-16
US15/621,327 US20170364890A1 (en) 2016-06-15 2017-06-13 System and method of payment of merchants on behalf of payment card system transaction acquirers

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US15/621,327 US20170364890A1 (en) 2016-06-15 2017-06-13 System and method of payment of merchants on behalf of payment card system transaction acquirers

Publications (1)

Publication Number Publication Date
US20170364890A1 true US20170364890A1 (en) 2017-12-21

Family

ID=59091668

Family Applications (6)

Application Number Title Priority Date Filing Date
US15/621,477 Abandoned US20170364879A1 (en) 2016-06-15 2017-06-13 Transaction flows and transaction processing for bridged payment systems
US15/621,383 Pending US20170364878A1 (en) 2016-06-15 2017-06-13 Systems and methods for bridging transactions between eft payment networks and payment card networks
US15/621,327 Pending US20170364890A1 (en) 2016-06-15 2017-06-13 System and method of payment of merchants on behalf of payment card system transaction acquirers
US15/622,594 Pending US20170364910A1 (en) 2016-06-15 2017-06-14 System and method to push payment to beneficiary account using an alias
US15/622,337 Pending US20170364880A1 (en) 2016-06-15 2017-06-14 System and method of tokenizing deposit account numbers for use at payment card acceptance point
US15/622,231 Pending US20170364918A1 (en) 2016-06-15 2017-06-14 Systems and methods for budget, financial account alerts management, remedial action controls and fraud monitoring

Family Applications Before (2)

Application Number Title Priority Date Filing Date
US15/621,477 Abandoned US20170364879A1 (en) 2016-06-15 2017-06-13 Transaction flows and transaction processing for bridged payment systems
US15/621,383 Pending US20170364878A1 (en) 2016-06-15 2017-06-13 Systems and methods for bridging transactions between eft payment networks and payment card networks

Family Applications After (3)

Application Number Title Priority Date Filing Date
US15/622,594 Pending US20170364910A1 (en) 2016-06-15 2017-06-14 System and method to push payment to beneficiary account using an alias
US15/622,337 Pending US20170364880A1 (en) 2016-06-15 2017-06-14 System and method of tokenizing deposit account numbers for use at payment card acceptance point
US15/622,231 Pending US20170364918A1 (en) 2016-06-15 2017-06-14 Systems and methods for budget, financial account alerts management, remedial action controls and fraud monitoring

Country Status (4)

Country Link
US (6) US20170364879A1 (en)
EP (6) EP3472791A1 (en)
CN (6) CN109564657A (en)
WO (6) WO2017218479A1 (en)

Families Citing this family (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10212158B2 (en) * 2012-06-29 2019-02-19 Apple Inc. Automatic association of authentication credentials with biometrics
US10331866B2 (en) 2013-09-06 2019-06-25 Apple Inc. User verification for changing a setting of an electronic device
US20150220931A1 (en) 2014-01-31 2015-08-06 Apple Inc. Use of a Biometric Image for Authorization
US10565364B1 (en) * 2015-12-28 2020-02-18 Wells Fargo Bank, N.A. Token management systems and methods
US10949863B1 (en) * 2016-05-25 2021-03-16 Wells Fargo Bank, N.A. System and method for account abuse risk analysis
US10817869B2 (en) 2016-06-29 2020-10-27 Square, Inc. Preliminary enablement of transaction processing circuitry
US11010765B2 (en) 2016-06-29 2021-05-18 Square, Inc. Preliminary acquisition of payment information
GB2551790A (en) * 2016-06-30 2018-01-03 Ipco 2012 Ltd A method, apparatus and system for electronic payments
WO2018009369A1 (en) * 2016-07-06 2018-01-11 Mastercard International Incorporated Method and system for providing sales information and insights through a conversational interface
US10915899B2 (en) * 2017-03-17 2021-02-09 Visa International Service Association Replacing token on a multi-token user device
US10706395B2 (en) * 2017-07-11 2020-07-07 American Express Travel Related Services Company, Inc. Fund transfer service for multiple linked transaction accounts
US20190295088A1 (en) * 2018-03-23 2019-09-26 Microsoft Technology Licensing, Llc System and method for efficient detection of fraud in online transactions
US20190325410A1 (en) * 2018-04-20 2019-10-24 Mastercard International Incorporated Methods and system for selecting payment system for transaction routing
US20200007647A1 (en) * 2018-06-28 2020-01-02 Bank Of America Corporation Real-time Event Orchestrator
US11182754B2 (en) * 2018-08-28 2021-11-23 Jpmorgan Chase Bank, N.A. Methods for synthetic monitoring of systems
US11049095B2 (en) 2018-12-21 2021-06-29 Square, Inc. Point of sale (POS) systems and methods with dynamic kernel selection
US10990969B2 (en) * 2018-12-21 2021-04-27 Square, Inc. Point of sale (POS) systems and methods for dynamically processing payment data based on payment reader capability
US10762196B2 (en) 2018-12-21 2020-09-01 Square, Inc. Point of sale (POS) systems and methods with dynamic kernel selection
US10984434B1 (en) 2019-07-02 2021-04-20 Wells Fargo Bank, N.A. Systems and methods for determining and providing non-financial benefits on a subscription basis
CN111192057B (en) * 2019-12-31 2021-10-15 网联清算有限公司 Payment processing method, device and system
CN111459054A (en) * 2020-04-14 2020-07-28 珠海格力电器股份有限公司 Recipe pushing method, equipment, storage medium and kitchen appliance
EP3951688A1 (en) * 2020-08-05 2022-02-09 Mastercard International Incorporated A method, system and computer program product for instructing a transfer from an account

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100030687A1 (en) * 2008-01-18 2010-02-04 Cashedge, Inc. Real-Time Settlement of Financial Transactions Using Electronic Fund Transfer Networks
US20100228672A1 (en) * 2009-03-03 2010-09-09 Quercus (BVI) Limited System and method for executing an electronic payment
US20100274729A1 (en) * 2002-05-24 2010-10-28 Don Holm System and Method for Varying Electronic Settlements Between Buyers and Suppliers with Dynamic Discount Terms

Family Cites Families (69)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6658568B1 (en) * 1995-02-13 2003-12-02 Intertrust Technologies Corporation Trusted infrastructure support system, methods and techniques for secure electronic commerce transaction and rights management
US5892900A (en) * 1996-08-30 1999-04-06 Intertrust Technologies Corp. Systems and methods for secure transaction management and electronic rights protection
US6636833B1 (en) * 1998-03-25 2003-10-21 Obis Patents Ltd. Credit card system and method
US20130191278A1 (en) * 1999-05-03 2013-07-25 Jpmorgan Chase Bank, N.A. Method and System for Processing Internet Payments Using the Electronic Funds Transfer Network
EP1132797A3 (en) * 2000-03-08 2005-11-23 Aurora Wireless Technologies, Ltd. Method for securing user identification in on-line transaction systems
US7225156B2 (en) * 2001-07-11 2007-05-29 Fisher Douglas C Persistent dynamic payment service
EP1482680A4 (en) * 2002-03-29 2010-01-27 Ntt Docomo Inc Communication control method in connection-type communication, related relay device, and accounting management device
US7275685B2 (en) * 2004-04-12 2007-10-02 Rearden Capital Corporation Method for electronic payment
US7603555B2 (en) * 2004-12-07 2009-10-13 Microsoft Corporation Providing tokens to access extranet resources
US20070100748A1 (en) * 2005-10-19 2007-05-03 Sanjeev Dheer Multi-channel transaction system for transferring assets between accounts at different financial institutions
CN101379501A (en) * 2005-12-20 2009-03-04 罗纳德·罗森伯格 Method, transaction card or identification system for transaction network
US8732044B2 (en) * 2006-05-23 2014-05-20 Mastercard International Incorporated Electronic transaction apparatus and method
WO2007149820A2 (en) * 2006-06-18 2007-12-27 Merrill Lynch & Co., Inc. Apparatuses, methods and systems for a deposit process manager decisioning engine
US20080015988A1 (en) * 2006-06-28 2008-01-17 Gary Brown Proxy card authorization system
US7739197B2 (en) * 2006-10-05 2010-06-15 International Business Machines Corporation Guest limited authorization for electronic financial transaction cards
CN101595491A (en) * 2006-12-26 2009-12-02 维萨美国股份有限公司 Mobile vending purchasing
CN101211439A (en) * 2006-12-26 2008-07-02 阿里巴巴公司 Method and system for accomplishing on-line payment in instant communication software
BRPI0810369B8 (en) * 2007-04-17 2019-05-28 Visa Usa Inc method, computer readable medium, directory server, and telephone
US8355982B2 (en) * 2007-08-16 2013-01-15 Verifone, Inc. Metrics systems and methods for token transactions
WO2010022129A1 (en) * 2008-08-20 2010-02-25 Xcard Holdings Llc Secure smart card system
GB2488059B (en) * 2009-01-06 2012-10-24 Bcs Information Systems Pte Ltd Electronic payment method of presentation to an automated clearing house (ACH)
US9230259B1 (en) * 2009-03-20 2016-01-05 Jpmorgan Chase Bank, N.A. Systems and methods for mobile ordering and payment
US9886693B2 (en) * 2009-03-30 2018-02-06 Yuh-Shen Song Privacy protected anti identity theft and payment network
US10089683B2 (en) * 2010-02-08 2018-10-02 Visa International Service Association Fraud reduction system for transactions
US20140095383A1 (en) * 2011-10-20 2014-04-03 Bindu Rama Rao System for anonymous funds transfer using adhoc staging accounts
US20110320291A1 (en) * 2010-06-28 2011-12-29 Coon Jonathan C Systems and methods for asynchronous mobile authorization of credit card purchases
US20120016799A1 (en) * 2010-07-16 2012-01-19 Patrick Killian Money transfer system gateway service
WO2012014231A1 (en) * 2010-07-29 2012-02-02 Nirmal Juthani System and method for generating a strong multi factor personalized server key from a simple user password
CN101958025B (en) * 2010-09-06 2014-06-18 广东铭鸿数据有限公司 Mobile phone payment method using barcode technology, and on-site payment terminal and system
US8719166B2 (en) * 2010-12-16 2014-05-06 Verizon Patent And Licensing Inc. Iterative processing of transaction information to detect fraud
US8583498B2 (en) * 2010-12-30 2013-11-12 Face It Corp. System and method for biometrics-based fraud prevention
US9760871B1 (en) * 2011-04-01 2017-09-12 Visa International Service Association Event-triggered business-to-business electronic payment processing apparatuses, methods and systems
US20120316992A1 (en) * 2011-06-07 2012-12-13 Oborne Timothy W Payment privacy tokenization apparatuses, methods and systems
US8700527B2 (en) * 2011-07-14 2014-04-15 Bank Of America Corporation Merchant bill pay
US20130240622A1 (en) * 2011-07-18 2013-09-19 Andrew H. B. Zhou Facilitating mobile device payments using mobile payment account, mobile barcode and universal digital mobile currency
US20130024358A1 (en) * 2011-07-21 2013-01-24 Bank Of America Corporation Filtering transactions to prevent false positive fraud alerts
US20130060708A1 (en) * 2011-09-06 2013-03-07 Rawllin International Inc. User verification for electronic money transfers
US10510056B2 (en) * 2011-11-02 2019-12-17 Mastercard International Incorporated Method and system for multiple payment applications
US20130151402A1 (en) * 2011-12-09 2013-06-13 Time Warner Cable Inc. Systems and methods for electronic payment using a mobile device for billing to a subscriber account
US9830595B2 (en) * 2012-01-26 2017-11-28 Visa International Service Association System and method of providing tokenization as a service
US10535064B2 (en) * 2012-03-19 2020-01-14 Paynet Payments Network, Llc Systems and methods for real-time account access
CN111899010A (en) * 2012-03-19 2020-11-06 派奈特支付网络有限责任公司 Method and system for processing payment transactions
US20140032407A1 (en) * 2012-07-24 2014-01-30 Shashi Kapur System and Method for Funds Transfer Processing
US20140250011A1 (en) * 2013-03-01 2014-09-04 Lance Weber Account type detection for fraud risk
US9092778B2 (en) * 2013-03-15 2015-07-28 Varsgen, Llc Bank account protection method utilizing a variable assigning request string generator and receiver algorithm
US9898717B2 (en) * 2013-03-25 2018-02-20 Paypal, Inc. Online remittance system with methodology for predicting disbursement times of online electronic funds transfers
US9208492B2 (en) * 2013-05-13 2015-12-08 Hoyos Labs Corp. Systems and methods for biometric authentication of transactions
US20150006386A1 (en) * 2013-06-28 2015-01-01 Sap Ag Offline mobile payment process
EP2824628A1 (en) * 2013-07-10 2015-01-14 Vodafone Holding GmbH Direct debit procedure
WO2015013548A1 (en) * 2013-07-24 2015-01-29 Visa International Service Association Systems and methods for interoperable network token processing
GB2516828A (en) * 2013-07-25 2015-02-11 Visa Europe Ltd Processing electronic tokens
US10902421B2 (en) * 2013-07-26 2021-01-26 Visa International Service Association Provisioning payment credentials to a consumer
US10460322B2 (en) * 2013-08-30 2019-10-29 Mastercard International Incorporated Methods and systems for verifying cardholder authenticity when provisioning a token
US20150134539A1 (en) * 2013-11-12 2015-05-14 Shashi Kapur System and method of processing point-of-sale payment transactions via mobile devices
US10861090B2 (en) * 2013-11-27 2020-12-08 Apple Inc. Provisioning of credentials on an electronic device using passwords communicated over verified channels
CN103745401A (en) * 2013-12-19 2014-04-23 镇江锐捷信息科技有限公司 Method for realizing remote credit and loan system on mobile terminal
US10127528B2 (en) * 2013-12-20 2018-11-13 Movocash, Inc. Financial services ecosystem
US20150199679A1 (en) * 2014-01-13 2015-07-16 Karthikeyan Palanisamy Multiple token provisioning
US9846878B2 (en) * 2014-01-14 2017-12-19 Visa International Service Association Payment account identifier system
US10373154B2 (en) * 2014-05-19 2019-08-06 Mastercard International Incorporated Apparatus, method, and computer program product for settlement to a merchant's card account using an on-line bill payment platform
US20150363752A1 (en) * 2014-06-13 2015-12-17 Mastercard International Incorporated Payment network with service provider directory function
US20160034889A1 (en) * 2014-07-29 2016-02-04 Mastercard International Incorporated Apparatus, method, and computer program product for automated sequential electronic payments
CN104268743B (en) * 2014-09-05 2017-11-14 哆啦宝（北京）科技有限公司 A kind of Mobile banking's payment system automatically generated based on Quick Response Code
US20160104122A1 (en) * 2014-10-10 2016-04-14 Bank Of America Corporation Remote video conferencing system
US20160112262A1 (en) * 2014-10-18 2016-04-21 Weaved, Inc. Installation and configuration of connected devices
CN104361490B (en) * 2014-11-03 2018-04-24 上海众人网络安全技术有限公司 A kind of method of payment and system of sensitive information markization
US11080701B2 (en) * 2015-07-02 2021-08-03 Royal Bank Of Canada Secure processing of electronic payments
CN104717628B (en) * 2015-03-31 2016-09-28 北京奇虎科技有限公司 For answering method, the Apparatus and system that behavior is paid
CN105139193B (en) * 2015-07-31 2017-04-12 腾讯科技（深圳）有限公司 Electronic resource processing method, electronic resource processing device and server

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100274729A1 (en) * 2002-05-24 2010-10-28 Don Holm System and Method for Varying Electronic Settlements Between Buyers and Suppliers with Dynamic Discount Terms
US20100030687A1 (en) * 2008-01-18 2010-02-04 Cashedge, Inc. Real-Time Settlement of Financial Transactions Using Electronic Fund Transfer Networks
US20100228672A1 (en) * 2009-03-03 2010-09-09 Quercus (BVI) Limited System and method for executing an electronic payment

Also Published As

Publication number Publication date
EP3472780A1 (en) 2019-04-24
WO2017218485A1 (en) 2017-12-21
CN109313766A (en) 2019-02-05
US20170364879A1 (en) 2017-12-21
EP3472781A1 (en) 2019-04-24
WO2017218489A1 (en) 2017-12-21
US20170364910A1 (en) 2017-12-21
EP3472789A1 (en) 2019-04-24
CN109564657A (en) 2019-04-02
EP3472782A1 (en) 2019-04-24
WO2017218483A1 (en) 2017-12-21
US20170364878A1 (en) 2017-12-21
WO2017218487A1 (en) 2017-12-21
US20170364880A1 (en) 2017-12-21
CN109313754A (en) 2019-02-05
CN109313764A (en) 2019-02-05
EP3472783A1 (en) 2019-04-24
WO2017218479A1 (en) 2017-12-21
EP3472791A1 (en) 2019-04-24
CN109313756A (en) 2019-02-05
US20170364918A1 (en) 2017-12-21
CN109313755A (en) 2019-02-05
WO2017218482A1 (en) 2017-12-21

Similar Documents

Publication Publication Date Title
US20170364890A1 (en) System and method of payment of merchants on behalf of payment card system transaction acquirers
US20210350345A1 (en) Systems and methods for point of sale deposits
RU2535463C2 (en) Apparatus and method for registering payment card for account settlement
US8712914B2 (en) Method and system for facilitating micropayments in a financial transaction system
US8447693B2 (en) Methods and systems for routing payment transactions
AU2016203358A1 (en) Using card image to extract bank account information
US20160034889A1 (en) Apparatus, method, and computer program product for automated sequential electronic payments
CA2958205C (en) Payroll system with flexible disbursement options
US20180308073A1 (en) Computerized system for resource deficiency triggered dynamic resource transfer
US20190108582A1 (en) Systems and methods for refunding qr and other payment system transactions
US10535067B2 (en) Electronic incremental payments
WO2016200609A1 (en) Systems and methods for extending credit to small/medium-sized enterprises
US20150199660A1 (en) Communication network for collecting data and executing electronic transaction services
US20160140557A1 (en) E-commerce based payment system with authentication of electronic invoices
US10621567B2 (en) Electronic grace period billing
US20190012645A1 (en) System and methods for accepting dual function payment credential
WO2020040916A1 (en) System and method for linking payment card to payment account
US20130073462A1 (en) Processing a Payment Transaction From a Mobile Device
US20190325410A1 (en) Methods and system for selecting payment system for transaction routing
US11282069B2 (en) Touchless virtual card payment automation
US20210256524A1 (en) Real-time resource tracking and lookup facility
US20190228405A1 (en) Provisioning of payment acceptance to payment account holders
US20130073461A1 (en) Processing a Payment Transaction Involving a Merchant Account and a Customer Account Associated with the Same Enterprise
US20190108512A1 (en) Token-based web authorized split transactions
US20170372435A1 (en) Methods and systems for processing records submissions for tax assessment

Legal Events

Date Code Title Description
AS Assignment

Owner name: MASTERCARD INTERNATIONAL INCORPORATED, NEW YORK

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MALHOTRA, SANDEEP;SUBRAMANIAM, SHANTHAN;LORBERG, DANA J;REEL/FRAME:042693/0540

Effective date: 20160621

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STCB Information on status: application discontinuation

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: ADVISORY ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STCB Information on status: application discontinuation

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STCB Information on status: application discontinuation

Free format text: FINAL REJECTION MAILED

STCV Information on status: appeal procedure

Free format text: NOTICE OF APPEAL FILED

STCV Information on status: appeal procedure

Free format text: EXAMINER'S ANSWER TO APPEAL BRIEF MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: TC RETURN OF APPEAL

STPP Information on status: patent application and granting procedure in general

Free format text: TC RETURN OF APPEAL

STCV Information on status: appeal procedure

Free format text: ON APPEAL -- AWAITING DECISION BY THE BOARD OF APPEALS