Patent Application
20160034889
The present invention relates generally to the electronic and computer arts, and, more particularly, to electronic payment techniques and the like.
Currently, the majority of payments between buyer and seller which pass through an intermediary are settled via paper check and have a significant time lag and a long settlement period. Time lags in payments are realized because both buyers and intermediaries want to preserve working capital, generally at the expense of suppliers who bear additional cost in financing the receivables, combined with requirements for getting paid before making payment.
Principles of the present invention provide techniques for automated sequential electronic payments. In one aspect, an exemplary method for automating sequential electronic payments, in a scenario where a buyer purchases at least one of goods and services from a seller via an intermediary, according to an aspect of the invention, includes the steps of obtaining, at at least one of the intermediary and/or a third party, an indication that payment to the intermediary from the buyer is appropriate. Responsive to the indication, the intermediary and/or third party initiates a pull payment, via a payment card network, for an on-file payment card account number of the buyer. Responsive to success of the pull payment, the intermediary and/or third party initiates a push payment to the seller.
Aspects of the invention contemplate the method(s) described herein performed by one or more entities herein, as well as facilitating of one or more method steps by the same or different entities. As used herein, “facilitating” an action includes performing the action, making the action easier, helping to carry the action out, or causing the action to be performed. Thus, by way of example and not limitation, instructions executing on one processor might facilitate an action carried out by instructions executing on a remote processor, by sending appropriate data or commands to cause or aid the action to be performed. For the avoidance of doubt, where an actor facilitates an action by other than performing the action, the action is nevertheless performed by some entity or combination of entities.
One or more embodiments of the invention or elements thereof can be implemented in the form of a computer program product including a tangible computer readable recordable storage medium with computer usable program code for performing the method steps indicated stored thereon in a non-transitory manner. Furthermore, one or more embodiments of the invention or elements thereof can be implemented in the form of a system (or apparatus) including a memory and at least one processor that is coupled to the memory and operative to perform exemplary method steps (e.g., when instructions from a persistent storage device are loaded into the memory to configure the processor). Yet further, in another aspect, one or more embodiments of the invention or elements thereof can be implemented in the form of means for carrying out one or more of the method steps described herein; the means can include (i) specialized hardware module(s), (ii) software module(s) stored in a non-transitory manner in a tangible computer-readable recordable storage medium (or multiple such media) and implemented on a hardware processor, or (iii) a combination of (i) and (ii); any of (i)-(iii) implement the specific techniques set forth herein. Transmission medium(s) per se and disembodied signals per se are defined to be excluded from the claimed means.
One or more embodiments of the invention can provide substantial beneficial technical effects, as will be appreciated by the skilled artisan from the discussion herein. For example, embodiments employing virtual card numbers provide increased security and/or reduce PCI requirements to the merchant and potentially the issuer as well.
These and other features and advantages of the present invention will become apparent from the following detailed description of illustrative embodiments thereof, which is to be read in connection with the accompanying drawings.
With regard to payment card and similar payments, attention should now be given to
The ICs 104, 114 can contain processing units 106, 116 and memory units 108, 118. Preferably, the ICs 104, 114 can also include one or more of control logic, a timer, and input/output ports. Such elements are well known in the IC art and are not separately illustrated. One or both of the ICs 104, 114 can also include a co-processor, again, well-known and not separately illustrated. The control logic can provide, in conjunction with processing units 106, 116, the control necessary to handle communications between memory unit 108, 118 and the input/output ports. The timer can provide a timing reference signal from processing units 106, 116 and the control logic. The co-processor could provide the ability to perform complex computations in real time, such as those required by cryptographic algorithms.
The memory portions or units 108, 118 may include different types of memory, such as volatile and non-volatile memory and read-only and programmable memory. The memory units can store transaction card data such as, e.g., a user's primary account number (“PAN”) and/or personal identification number (“PIN”). The memory portions of units 108, 118 can store the operating system of the cards 102, 112. The operating system loads and executes applications and provides file management or other basic card services to the applications. One operating system that can be used to implement some aspects or embodiments of the present invention is the MULTOS® operating system licensed by MAOSCO Limited. (MAOSCO Limited, St. Andrews House, The Links, Kelvin Close, Birchwood, Warrington, Wash. 3 7PB, United Kingdom) Alternatively, JAVA CARD™-based operating systems, based on JAVA CARD™ technology (licensed by Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, Calif. 95054 USA), or proprietary operating systems available from a number of vendors, could be employed. Preferably, the operating system is stored in read-only memory (“ROM”) within memory portion 108, 118. In an alternate embodiment, flash memory or other non-volatile and/or volatile types of memory may also be used in the memory units 108, 118.
In addition to the basic services provided by the operating system, memory portions 108, 118 may also include one or more applications. At present, one possible specification to which such applications may conform is the EMV interoperable payments specification set forth by EMVCo, LLC (901 Metro Center Boulevard, Mailstop M3-3D, Foster City, Calif., 94404, USA). It will be appreciated that applications can be configured in a variety of different ways.
The skilled artisan will also be familiar with the MasterCard® PayPass™ specifications, available under license from MasterCard International Incorporated of Purchase, N.Y., USA (marks of MasterCard International Incorporated of Purchase, N.Y., USA).
As noted, cards 102, 112 are examples of a variety of payment devices that can be employed. The primary function of the payment devices may not be payment, for example, they may be cellular phone handsets that implement appropriate techniques. Such devices could include cards having a conventional form factor, smaller or larger cards, cards of different shape, key fobs, personal digital assistants (PDAs), appropriately configured cell phone handsets, or indeed any device with the appropriate capabilities. In some cases, the cards, or other payment devices, can include body portions (e.g., laminated plastic layers of a payment card, case or cabinet of a PDA, chip packaging, and the like), memories 108, 118 associated with the body portions, and processors 106, 116 associated with the body portions and coupled to the memories. The memories 108, 118 can contain appropriate applications. The processors 106, 116 can be operative to execute one or more steps. The applications can be, for example, application identifiers (AIDs) linked to software code in the form of firmware plus data in a card memory such as an electrically erasable programmable read-only memory (EEPROM).
A number of different types of terminals can be employed with system 100. Such terminals can include a contact terminal 122 configured to interface with contact-type device 102, a wireless terminal 124 configured to interface with wireless device 112, a magnetic stripe terminal 125 configured to interface with a magnetic stripe device 150, or a combined terminal 126. Combined terminal 126 is designed to interface with any combination of devices 102, 112, 150. Some terminals can be contact terminals with plug-in contactless readers. Combined terminal 126 can include a memory 128, a processor portion 130, a reader module 132, and optionally an item interface module such as a bar code scanner 134 and/or a radio frequency identification (RFID) tag reader 136. Items 128, 132, 134, 136 can be coupled to the processor 130. Note that the principles of construction of terminal 126 are applicable to other types of terminals and are described in detail for illustrative purposes. Reader module 132 can, in general, be configured for contact communication with card or device 102, contactless communication with card or device 112, reading of magnetic stripe 152, or a combination of any two or more of the foregoing (different types of readers can be provided to interact with different types of cards e.g., contacted, magnetic stripe, or contactless). Terminals 122, 124, 125, 126 can be connected to one or more processing centers 140, 142, 144 via a computer network 138. Network 138 could include, for example, the Internet, or a proprietary network (e.g., a virtual private network (VPN) such as is described with respect to
Many different retail or other establishments, represented by points-of-sale 146, 148, can be connected to network 138. Different types of portable payment devices, terminals, or other elements or components can combine or “mix and match” one or more features depicted on the exemplary devices in
Portable payment devices can facilitate transactions by a user with a terminal, such as 122, 124, 125, 126, of a system such as system 100. Such a device can include a processor, for example, the processing units 106, 116 discussed above. The device can also include a memory, such as memory portions 108, 118 discussed above, that is coupled to the processor. Further, the device can include a communications module that is coupled to the processor and configured to interface with a terminal such as one of the terminals 122, 124, 125, 126. The communications module can include, for example, the contacts 110 or antennas 120 together with appropriate circuitry (such as the aforementioned oscillator or oscillators and related circuitry) that permits interfacing with the terminals via contact or wireless communication. The processor of the apparatus can be operable to perform one or more steps of methods and techniques. The processor can perform such operations via hardware techniques, and/or under the influence of program instructions, such as an application, stored in one of the memory units.
The portable device can include a body portion. For example, this could be a laminated plastic body (as discussed above) in the case of “smart” or “chip” cards 102, 112, or the handset chassis and body in the case of a cellular telephone, tablet, or the like.
It will be appreciated that the terminals 122, 124, 125, 126 are examples of terminal apparatuses for interacting with a payment device of a holder. The apparatus can include a processor such as processor 130, a memory such as memory 128 that is coupled to the processor, and a communications module such as 132 that is coupled to the processor and configured to interface with the portable apparatuses 102, 112, 150. The processor 130 can be operable to communicate with portable payment devices of a user via the communications module 132. The terminal apparatuses can function via hardware techniques in processor 130, or by program instructions stored in memory 128. Such logic could optionally be provided from a central location such as processing center 140 over network 138. The aforementioned bar code scanner 134 and/or RFID tag reader 136 can optionally be provided, and can be coupled to the processor, to gather attribute data, such as a product identification, from a UPC code or RFID tag on a product to be purchased.
The above-described devices 102, 112 can be ISO 7816-compliant contact cards or devices or NFC (Near Field Communications) or ISO 14443-compliant proximity cards or devices. In operation, card 112 can be touched or tapped on the terminal 124 or 128 (or an associated reader), which then contactlessly transmits the electronic data to the proximity IC chip in the card 112 or other wireless device.
One or more of the processing centers 140, 142, 144 can include a database such as a data warehouse 154.
For completeness, it should be noted that the system depicted in
In some cases, there can be payment card accounts which do not have physical cards or other physical payment devices associated therewith; for example, a customer can be provided with a PAN, expiration date, and security code but no physical payment device, and use same, for example, for card-not-present telephone or internet transactions. In this regard, a “cardholder” should be understood to refer to the account holder of a payment card account, regardless of whether the holder actually has a physical payment card or other physical payment device.
With reference to
During a conventional credit authorization process, the cardholder 2002 pays for the purchase and the merchant 2004 submits the transaction to the acquirer (acquiring bank) 2006. The acquirer verifies the card number, the transaction type and the amount with the issuer 2010 and reserves that amount of the cardholder's credit limit for the merchant. At this point, the authorization request and response have been exchanged, typically in real time. Authorized transactions are stored in “batches,” which are sent to the acquirer 2006. During subsequent clearing and settlement, the acquirer sends the batch transactions through the credit card association, which debits the issuers 2010 for payment and credits the acquirer 2006. Once the acquirer 2006 has been paid, the acquirer 2006 pays the merchant 2004.
It will be appreciated that the network 2008 shown in
Messages within a network such as network 138 and/or network 2008, may, in at least some instances, conform to the International Organization for Standardization (ISO) Standard 8583, Financial transaction card originated messages—Interchange message specifications, which is the ISO standard for systems that exchange electronic transactions made by cardholders using payment cards. It should be noted that the skilled artisan will be familiar with the ISO 8583 standards. Nevertheless, out of an abundance of caution, the following documents are expressly incorporated herein by reference in their entirety for all purposes (published by ISO, Geneva, Switzerland, and available on the ISO web site):
As used herein, a “payment card network” is a communications network that uses payment card account numbers, such as primary account numbers (PANs), to authorize, and to facilitate clearing and settlement of, payment card transactions for credit, debit, stored value and/or prepaid card accounts. The card accounts have standardized payment card account numbers associated with them, which allow for efficient routing and clearing of transactions; for example, ISO standard account numbers such as ISO/IEC 7812-compliant account numbers. The card accounts and/or account numbers may or may not have physical cards or other physical payment devices associated with them. For example, in some instances, organizations have purchasing or procurement card accounts to which a payment card account number is assigned, used for making purchases for the organization, but there is no corresponding physical card. In other instances, “virtual” account numbers are employed; this is also known as PAN mapping. The PAN mapping process involves taking the original Primary Account Number (PAN)(which may or may not be associated with a physical card) and issuing a pseudo-PAN (or virtual card number) in its place. Commercially available PAN-mapping solutions include those available from Orbiscom Ltd., Block 1, Blackrock Business Park, Carysfort Avenue, Blackrock, Co. Dublin, Ireland (now part of MasterCard International Incorporated of Purchase, N.Y., USA); by way of example and not limitation, techniques of U.S. Pat. Nos. 6,636,833 and 7,136,835 of Flitcroft et al., the complete disclosures of both of which are expressly incorporated herein by reference in their entireties for all purposes.
Some payment card networks connect multiple issuers with multiple acquirers; others use a three party model. Some payment card networks use ISO 8583 messaging. Non-limiting examples of payment card networks that connect multiple issuers with multiple acquirers are the BANKNET® network and the VISANET® network. One or more embodiments are applicable to many other different kinds of payment card networks as well; the AMERICAN EXPRESS® network and the DISCOVER® network are non-limiting examples.
Still referring to
More specifically, the acquirer 2006, in the more specific example of
The acquirer 2006 will present transactions from many different merchants 2004 to the payment card network operator 2008 via the PNIP interface 2012. The connection between the merchants 2004 and the acquirer 2006 is typically a TCP/IP interface 2016. The format that the transaction is in when the card is swiped at the merchant 2004 may differ from the format that the transaction is in when actually received by the payment card network operator. The acquirer may convert the transaction into the ISO 8583 format or into a format that is a specific implementation of the ISO 8583 format (e.g., the MASTERCARD CIS (customer interface specification) format. The authorization request message can be an ISO 8583 message type identifier (MTI) 0100 message, for example, sent over the communications interface 2016 between the merchant 2004 and the acquirer 2006.
Once the 0100 message is received at the PNIP 2012 of the acquirer 2006, a series of edits can be performed on the transaction with respect to format, content, and/or context. Furthermore, screening can be carried out to determine whether the message relates to something beyond an ordinary authorization request, referred to as an enhanced service. Enhanced services may be screened for on behalf of one or more issuers 2010 and/or the operator of network 2008 itself. A centralized member parameter system (MPS) 2018 can be provided to house parameters used to drive processing of credit authorization transactions. In one or more embodiments, extracts from the centralized member parameter system 2018 are distributed to all acquirer PNIPs 2012 and issuer PNIPs 2024 on the network 2008 on a daily basis to drive processing of credit card transactions.
It should be noted at this point that an “ICA” and a “BIN” are employed in BANKNET so that a member can perform card issuing and/or acquiring activities. An ICA or Interbank Card Association is a four to six digit identification assigned by MasterCard for use by a member to uniquely identify activity the member is responsible for. A BIN or Bank Identification Number is a unique series of numbers assigned by MasterCard to a principal member and used as the first six digits of a cardholder account number. Other payment card networks have similar types of numbers, as will be apparent to the skilled artisan.
In at least some embodiments, the same member parameter extract is sent to all PNIPs and transactions are routed using same. In at least some circumstances, account numbers or ranges of account numbers are used in deciding how to route. In some cases, transactions are routed to an issuer PNIP based on where the account range is “signed in.” Issuers send an MTI 0800 sign in request message with either a group ID or account range. The Member ID is pulled from the PNIP port 2038 configuration and transactions from that account range are then routed to the port from which the sign-in request is received. A member ID can be present on ports on multiple PNIPs at an Issuer site—see discussion of
In one or more embodiments, based on the account range, the parameters in MPS 2018 (or a local extract thereof) will determine how to process a given transaction; e.g., product code, country code, currency code, and the like, including what enhanced services (if any) the issuer has signed up for on a particular account range. That is to say, the messages are parsed and certain fields, including the account range, are examined; the account range is associated with a certain issuer and based on that, the message may be treated differently. Messages may be parsed, and converted into an internal data format so that access can be obtained to all the individual data elements. In one or more embodiments, the account number is used as a key to access the MPS 2018 (or a local extract thereof) and retrieve all the parameters that are appropriate for processing the given transaction. In a non-limiting example, a suitable message parser 2020 (and other programs on the PNIP 2012) can be written in an appropriate high-level language or the like.
In an exemplary embodiment, the central MPS 2018 creates extracts once a day that are distributed out to the endpoints on the network (e.g., PNIPs 2012), as seen at 2022. These extracts include the pertinent information needed for the PNIP to process the message and determine if it requires any special handling. In some instances, messages are next routed to a central site 2009 for performance of enhanced services. On the other hand, if no special services are required, the message may be routed directly to the issuer PNIP 2024 as seen at 2026.
Messages routed directly to the issuer PNIP: In this aspect, the transaction is routed directly to the issuer PNIP 2024 based on the MPS extract 2022, as seen at 2026. Every account range will have a unique destination endpoint identified in the parameters (account ranges may be grouped and all members of the account range group may have a common destination endpoint). The member interface refers to the connection between the acquirer processor 2006 and the Acquirer PNIP 2012. This term also applies to the interface between the Issuer PNIP 2024 and issuer processor 2010. The connections between and among acquirer PNIP 2012 and issuer PNIP 2024, acquirer PNIP 2012 and ASPs 2050, and ASPs 2050 and issuer PNIP 2024 are referred to as a network interface onto the payment card network itself. In one or more embodiments, this may be a TCP/IP connection (as seen at 2026) with customized routing capabilities including group addresses. Normally, TCP/IP addresses refer to a single endpoint. Group addresses may be directed to a group of addresses, and will target any of the computers (e.g., PNIPs) in the group using a variety of protocols. Some use a round robin approach; others may use a first in list approach where the message is always routed to one given computer first and then to a second computer only if the first is not available. Group addressing may be useful, for example, where an acquirer or issuer has multiple PNIPS at the same location for redundancy/fault tolerance. It is also possible to combine the approach and institute a round robin, wherein the addresses within the round robin are first in list group address, or conversely, it is possible to institute a first-in-list, wherein the addresses within the first-in-list are round robin group addresses. These capabilities are useful in case of outages, maintenance, and the like.
As seen in
At this point, the 0100 message has been delivered to the issuer 2010. The issuer 2010 then carries out issuer processing and decisioning (e.g., with issuer processing platform 2040) based on transaction velocities, open to buy, fraud detection protocols, etc., and provides an appropriate authorization request response, ISO 8583 MTI 0110. There are a number of different possible response codes defined within ISO 8583 and its particular implementations. Each transaction is made up of multiple data elements; the response from the issuer is included in data element 39. Once the 0110 message is received on the issuer PNIP 2024 from platform 2040 it is parsed and edited for format, content, and context, including validation of DE39 to make sure that it is a valid value.
It is worth noting that in one or more instances, at every point where a transaction touches a computer of the payment card network, whether it be an acquirer PNIP 2012, issuer PNIP 2024, or a special services computer or computers 2050 at the central location 2009 (discussed below), transaction context is preserved. That is to say, before the message is sent on to the next node in the network, a copy is saved in a context manager queue 2042, 2046, 2058, so that when the transaction response MTI 0110 comes back through, the request MTI 0100 can be matched with the response, in order to know how to route the response back to the previous route point. One of the items saved in the context manager queue is the message originator's address, so that it can be used for route-back information. Once the issuer PNIP validation is complete, including format, content, and context edits, the transaction is extracted from the context manager queue 2046 and the route-back address is retrieved, and the 0110 message is then sent back where it came from; in this case, the acquirer PNIP 2012 (or ASP 2050). The acquirer PNIP 2012 then receives and parses the message and pulls its original request out of its context manager queue 2042. Note that multiple acquirers may share an acquirer PNIP and it is therefore necessary to know which port on the acquirer PNIP to route the response back to (see discussion of
Each PNIP 2012, 2024 typically has many different programs. These can include, for example, a parser/editor 2020, 2043; a parameter file manager; a transaction context manager; a member communications program; a network communications program; and the like. Please note that to reduce clutter,
Messages in case of Enhanced Services: In one or more instances, a special architecture is used to facilitate delivery of enhanced services (the ASP 2050 in
On the acquirer PNIP 2012, when checking the member parameter file for an account range, determine whether the transaction requires enhanced services. If yes, the transactions is routed to the central site ASPs 2050, which have interfaces to all of the service provider systems—the ASPs do not necessarily provide the services themselves (although they can in some embodiments), but may mediate between the network (e.g., BANKNET) and the actual service providers 2051-1 through 2051-N. An ASP will typically have connections 2053 to a mainframe 2052 via DB2 connect or other suitable connection. If a transaction is to be enriched with additional data, a database call will be made to the mainframe 2052 to retrieve the information from mainframe database 2054 so that it can be inserted into the transaction before the transaction is forwarded to the issuers. Interfaces can also be provided to a risk management system, a decisioning management system, IN CONTROL, rewards, and the like. Service providers 2051-1 through 2051-N generally represent any enhanced services, non-limiting examples of which have been given herein.
A communications layer 2056 is used to communicate with the service providers in one or more embodiments, a non-limiting example of a suitable implementation is the IBM MQ series. The 0100 message may be sent to the service providers, optionally encapsulated inside a special “enhanced services” (ES) header that wraps the message with any additional information required to fulfill the service. The service provider sends a response. The ASP takes the response and enriches the 0100 transaction with the service response, and then sends the entire package on to the issuer PNIP 2024. Some enhanced services are processed on the request messages (0100) and others are processed on the response messages (0110). Once the response message is processed on the ASP, the original message will be pulled from the context manager queue 2058 on the ASP to determine the appropriate acquirer PNIP 2012 to route the message back to. From there, the acquirer PNIP will behave just as in the “Messages routed directly to the issuer PNIP” case discussed above. Some embodiments of the special architecture use an Enterprise Service Bus to mediate and facilitate some of the services 2051. For example, the In CONTROL service can be accessed via an instance of an Enterprise Service Bus.
Entry of Data into the Data Warehouse: In one or more instances, every transaction that flows through the issuer PNIP 2012, acquirer PNIP 2024, and/or ASPs 2050 is logged at every point by writing log records. Multiple times a day (e.g., six), a global file transfer system 2059 pulls the logs off each node and collects them into a support files system 2060 on the mainframe 2052. The log files are parsed and collected into a general daily file. The general daily file is scrubbed and modified to create a consolidated file on the mainframe which is then pulled into the data warehouse 2062, where additional data manipulation and scrubbing are performed before the transactions are stored. The data warehouse 2062 is located at an intermediate node (location 2009) connected to the PNIPs of the acquirers and issuers 2012, 2024. By way of clarification, in one or more embodiments, the node 2009 is directly connected to the PNIPs 2012, 2024 but the data warehouse is not directly connected to the 2012 and 2024 devices; rather, data flows through GFT and SF systems 2059, 2060 and ends up in the data warehouse. Data warehouse 2062 should be distinguished from a data warehouse 154 that might be maintained by an issuer.
Clearing and Settlement: One or more instances employ a clearing and settlement system 2074. In clearing, via global file transfer 2059, acquirers submit clearing files in an appropriate message format (in a non-limiting example, Integrated Product Messages (IPM) format). The files contain, from the acquirers' perspective, what they believe they should be paid for. In one or more instances, the authorization does not actually move any money; the authorization only validates that the cardholder is a valid cardholder recognized by the bank, which will honor payment to the merchant for the goods or services. For example, in a typical restaurant visit, the card is swiped for the receipt amount but then a tip is added. The clearing message will have the actual food amount plus the tip. In one or more instances, the clearing does not actually move the money; it merely resolves the actual amounts. The settlement system actually initiates movement of the money. Furthermore in this regard, the settlement system actually tells the banks how much money to move but does not actually move the money. Within clearing, processes include dispute resolution, chargeback, and the like. During clearing, files are sent from the acquirers to the payment card network; the payment card network, using clearing and settlement system 2074, then takes the files and splits them and sorts them by issuer. Response files are then received from each issuer, and these response files are again split and re-sorted back to the correct acquirers. Eventually, data flows into the settlement system and money is moved. Thus, at a high level, the auth request and auth request response are in real time, and the clearing and settlement are in a batch mode.
By way of review and provision of additional detail, in at least some instances, in a batch mode, clearing is initiated via an ISO 8583 MTI 1240 message having a DE24 function code value of 200 for a first presentment. Once this message is obtained from the acquirer, the payment card network, using clearing and settlement system 2074, will undertake syntax edits, format edits, content edits, and context edits (typically applied to every transaction). If those edits are passed, the interchange and fees associated with the transaction will be calculated. Based on the calculations, the message may also be enriched with additional information before being passed on to the issuer. The settlement amount is then determined. Within the clearing cycle, the amounts of money due to each given member (e.g., issuer or acquirer) are accumulated, and these are summed up into a settlement file which is forwarded in due course.
Cryptographic aspects: Consider the concepts of data at rest and data in motion. An example of data at rest is the log files that actually reside on the PNIPS themselves—configuration information containing card numbers or personally identifiable information (PII). In one or more embodiments, all sensitive data at rest is encrypted before being written to disk. Data in motion refers to data actually moving over a transmission medium (e.g., wires, coaxial cable, fiber optic cable, RF link). All PCI-sensitive data (PCI Security Standards Council, LLC, Wakefield, Mass. US) is encrypted, whether written to disk or being sent over a network. In at least some instances, internal links within the premises of the acquirers and issuers are not encrypted since it is assumed that the customer premises are a physically secure facility relying on physical security of the hardware. On the other hand, in at least some instances, external links (e.g., links 2026, 2030 and 2032) are all encrypted for both authorization traffic and bulk file transfers.
One or more embodiments will have interface(s) 2068 to other brands of payment card processing network. For example, a MASTERCARD branded payment card processing network may have interfaces to networks such as AMERICAN EXPRESS, VISA, JCB, DISCOVER, and the like. Suitable translation layers can be provided to intermediate between MASTERCARD (or other) format and formats used by other networks, as appropriate. In one or more embodiments, interfaces 2068 to other payment networks are provided via a machine, located at 2009, but generally analogous to an Issuer PNIP 2024 with added mediation layers loaded as required by other payment network formats. Some merchants may only have a single interface to, e.g., the MASTERCARD network—all transactions from that merchant may be routed to MASTERCARD, regardless of what card was used—MASTERCARD will process those transactions and route them out to the appropriate networks.
While payment card networks have generally been used as described with regard to
US Patent Publication 2014-0067620 of Blinov, expressly incorporated herein by reference in its entirety for all purposes, discloses techniques for purchasing by crediting a merchant's card, in connection with an on-line purchase of goods.
Electronic Bill Presentment and/or Payment Systems
The process of electronic bill presentment and payment has also been popular for quite some time. For example, U.S. Pat. No. 5,699,528 to Hogan, expressly incorporated herein by reference in its entirety for all purposes, discloses a system and method for bill delivery and payment over a communications network. In the bill delivery and payment system, users are able to access a server computer on a communications network to obtain bill information and pay bills.
Referring now to
Electronic bill presentment and payment systems can be used in connection with some embodiments; one example is the MASTERCARD RPPS® electronic payment system of MasterCard International Incorporated of Purchase, N.Y., USA. This example is non-limiting; for example, other types of electronic bill presentment and/or payment systems could be employed in other instances. Non-limiting examples are described in:
For the avoidance of doubt, references to MasterCard, unless expressly stated to be limited to MasterCard, are intended to be exemplary of an operator of an electronic bill payment system (optionally, with presentment functionality), an operator of a payment card network, and/or an operator of a virtual card number generator, as will be appreciated from the context, whether or not qualified by words such as “or other operator.”
Furthermore, another non-limiting example of an electronic bill presentment and/or payment system that could be used in connection with some embodiments of the invention is the CHECKFREE platform available from Fiserv, Inc. of Brookfield, Wis., USA. Other possibilities will also be apparent to the skilled artisan, given the teachings herein.
In a payment phase, consumer 1010 sends bill payment instructions to CSP 1008, as seen at 1020. CSP 1008 in turn sends the bill payment information to the system 1006, as at 1022. The system sends funds and data electronically to BSP 1004, as at 1024. The BSP 1004 posts payment information to the biller 1002, as at 1026.
Note that “BPPS” is used herein as shorthand for an electronic “bill presentment and payment system”; the MASTERCARD RPPS system is a non-limiting example of such a system.
Note that in some instances, billers 1002 can connect directly to BPPS 1006 without the use of BSP 1004. In such cases, billers 1002 exchange presentment and payment data directly with BPPS 1006.
As used herein, an “electronic bill presentment system using customer service providers” refers to a system wherein electronic bills are distributed from billers, through an aggregator switch, out to financial institutions or other customer service providers such that those financial institutions or other customer service providers can display the electronic bills, through the financial institutions' or other customer service providers' own on-line banking interface, to bill-paying customers of the financial institutions or other customer service providers.
Some electronic bill payment systems use the NACHA ACH Standard Entry Class (SEC) formats, such as CIE (Customer Initiated Entries), CTX (Corporate trade exchange); CCD (Cash Concentration or Disbursement); or PPD (Prearranged payment and deposits). Some electronic bill payment systems use a modified form of the NACHA CIE (MOD-CIE) wherein a payment system operator requires specific values for certain fields. Some electronic bill payment systems (e.g., MASTERCARD RPPS) provide translation capability and can receive input in many different formats, translate it for internal use, and translate it again for output in many different formats, which may be the same as or different from the input formats. Some electronic bill payment systems provide customer service providers with the capability to specify when the electronic bill payment system will look to them for payment instructions. Some electronic bill payment systems provide biller service providers with the capability to specify when the electronic bill payment system will initiate payments.
As noted above, electronic bill presentment and payment systems are conceptually different than payment card networks, and will often use electronic funds transfer from a demand deposit account. Nevertheless, some electronic bill presentment and/or payment systems receive and send data over a network such as is shown in
Some electronic bill payment systems use technology such as described in the herein-referenced US Patent Publication 2013-0290177 A1 of Milam and Klaus to reduce the number of non-electronic payments. Some electronic bill payment systems use technology such as described in the herein-referenced US Patent Publication 2013-0311362 A1 of Amy C. Milam et al. to facilitate approximately matching entered payee information to stored biller information.
Note that currently, in some circumstances (such as the advertising scenario shown in
One or more embodiments automate sequential payments when an intermediary is leveraged to manage the relationship between a buyer and a seller. One or more embodiments combine and automate pull and push payments to help neutralize the bottleneck which is commonly created when an intermediary is used.
One or more embodiments accomplish one or more of the following:
Following service delivery, Media Supplier 506 invoices Ad Agency 504 according to the normal invoicing schedule (e.g. Net 30 terms); Ad Agency 504 subsequently invoices the End-Corporate 502 for the amount due. Upon invoice maturity, Ad Agency 504 “pulls” payment from the End-Corporate Lodged Card (T=31) (“T=” notations herein are non-limiting exemplary times in days). Upon receiving authorization for settlement of the End-Corporate invoice, Ad Agency 504 then “pushes” Virtual Card number to Supplier (T=32); this step can be automated to further streamline the process. End-Corporate 502 and Ad Agency 504 both settle transactions with Issuer 651 upon conclusion of the billing period (e.g. T=61-63). In the example shown, invoicing is assumed to take place after advertising services have been rendered, and disputes are assumed to be addressed in the 30 day invoicing period between the End-Corporate 502, Agency 504, and Supplier 506.
The “Pull-and-Push” payment process advantageously addresses several shortcomings in the current payment process used by End-Corporates, Agencies, and Suppliers. The “Pull-and-Push” solution speeds payment to Media Suppliers by one, some, or all of the following:
Issuers and Acquirers can facilitate a “Pull-and-Push” payment process by, for example, one, some, or all of the following:
Push-pull can also be facilitated by providing system (e.g., system 802 discussed below) that automatically generates a push payment upon receipt of the authorization code from a pull payment.
As noted, in one or more embodiments, this “pull” payment triggers a series of additional events. For example, once the “pull” occurs, a payment is directed to the media supplier 506—such payment can be in the form of a virtual card “push” as seen in step 606 on day 32. That is to say, ad agency 504 (and/or a third party as discussed below), with payment in hand from corporate client 502, uses technology in accordance with one or more embodiments of the invention to automate the creation and distribution of a virtual payment card number to the media supplier 506. Advantageously, this significantly reduces the amount of time between the media supplier 506 presenting its invoice to the ad agency 504 and the media supplier 506 ultimately being paid.
In a “pull” payment, the entity to be paid initiates the payment; in a “push” payment, the entity doing the paying initiates the payment. Stated in another way, in a “pull” payment, the card account is processed by the merchant using existing point-of-sale or point-of-interaction technology with the merchant's acquirer; in a “push” payment, the buyer rather than the supplier or merchant pushes the information to the merchant's acquirer (e.g., via a gateway such as the electronic transaction apparatus described in U.S. Pat. No. 8,732,044 of Lovelett, et al., expressly incorporated herein by reference in its entirety for all purposes). Suitable alternate terminology is “supplier initiated payment” (same as PULL—entity to be paid (or third party as discussed) has card number and will “hit” number) and “buyer initiated payment” (PUSH—buyer only gives the entity to be paid (or third party as discussed) the card number and directs that entity to “hit” the card when buyer is ready to). Note that “buyer” and “supplier” in this context refer to parties locally within the transaction. For example, in step 605 the ad agency is functioning as the supplier to the corporate client (“buyer”) 602. A payment card (e.g., purchasing card) of the corporation 502 is lodged at agency 504 (or third party as discussed) and, only upon approval of the corporate client 502, the ad agency 504 (or third party as discussed) is allowed to initiate a transaction using the previously-lodged purchasing card. This in turn causes the virtual card push payment to the media supplier 506 in step 606.
As an aside, it is worth noting at this point that in some instances, an auto-approve feature is provided whereby the ad agency pulls funds via an on-file account based on specific conditions agreed to with end corporate; for example where media placement occurs as ordered by end-corporate and an invoice can be provided post-payment for auditing purposes.
In at least some instances, there are steps and/or conditions that should be satisfied prior to or between “hitting” the lodged card in step 605 and initiating the virtual card payment in step 606. For example, in some embodiments, the ad agency 504 must provide proof to the corporate client 502 that the media purchases that were intended to be made were in fact made with the media supplier 506. Once this aspect is reconciled, then the ad agency 504 (or third party as discussed) can “hit” the lodged card for the payment. That is to say, in at least some cases, some type of proof of delivery of the services is required. Furthermore in this regard, in some cases, the invoice will be reviewed between T=1 and T=31. Corporate client 502 looks at the invoice and ensures that it is ready for payment; i.e., that all obligations have been met.
Again, for the avoidance of doubt, while non-limiting examples are given herein in the context of media reconciliation, many other situations involve intermediaries and can potentially benefit from use of one or more embodiments of the invention to reduce “bottleneck” issues. For example, consider a law firm that represents a corporation and hires local counsel for filing in foreign countries (“foreign associates”). The law firm fulfills the role of the agency 504 and the foreign associates take on the role of the media supplier 506.
Consider now step 607, “agency receives cash @ T=33.” When ad agency 504, acting as a merchant with respect to end-corporate 502, charges the lodged card at T=31 in step 605, 2-3 days later the agency 504 will receive payment through the ad agency's merchant bank (“acquirer,” “acquiring bank,” and “merchant bank” are used synonymously herein), from the issuer 651, via a payment card network (e.g., BANKNET or similar network 2008). This is reflected by the notation T=33 associated with step 607 (assumes 2 days elapsed from T=31). The third party could charge the lodged card on behalf of the agency. As an aside, please note the double-headed arrow linking card issuer 651 and ad agency 504; the upward direction represents step 607 and the downward direction represents step 610, discussed below. Now continuing, in step 608, at T=34 (for example), when the media supplier 506 accepts the card that they are sent by the ad agency 504, they (the media supplier) will also be paid in 2-3 days (T=34 assumes 2 days elapsed from T=32). The third party could send the card on behalf of the agency. In one or more embodiments, media supplier 506 receives a virtual card number in step 606; media supplier 506 uses that card number to send a conventional authorization request into BANKNET; that request is processed normally (authorization request response and subsequent clearing and settlement in batch mode, e.g.). Steps 607 and 608 satisfy the accounts receivable for both the agency 504 and the supplier 506—both suppliers (i.e., agency 504 and media supplier 506) have been paid at this point; the bank (issuer 651) has not yet been paid. Generally, there is a thirty day cycle or term on credit cards. In step 609, at T=61, 30 days after the agency 504 or third party acting on its behalf “hits” the lodged card of corporate client 502, the corporate client 502 pays the bank (issuer 651). Similarly, at T=63, step 610, the ad agency 504 pays the bank (issuer 651) for the charge that was sent to the media supplier 506.
Non-limiting examples will now be provided of one or more particular machines suitable for practicing the steps of one or more embodiments, as well as comments on how the functioning of such machine(s) can be improved using one or more aspects of the invention.
Steps 601 and 602: These steps can be implemented using a variety of techniques, such as a phone call, informal sketch or verbal instructions delivered in person, e-mail, conventional postal mail, or the like. In some instances, sophisticated third party software systems such as those available from Mediaocean, New York, N.Y., USA; Advantage Software, Inc., Mooresville, N.C., USA; and/or Strata Marketing, Inc., Chicago, Ill., USA; can be used.
In some embodiments, data is transferred from third party systems to a system 802 in accordance with one or more embodiments, in order to carry out reconciliation. For example, the third party might provide data indicating that an ad placement met the conditions of the ad buy (in terms of rating, e.g.). The rating data is then applied against the conditions in the system to allow the process to move forward to the next step (pull and push process). Thus, in one or more embodiments, a new interface is provided from a third party system to indicate that payment is appropriate because the required media has been purchased and has met its rating requirements (e.g., sufficient impressions). Marketron Inc. of Hailey, Idaho, USA provides pertinent data that can be used in one or more embodiments. In at least some instances, Marketron data acts like an invoice to verify that something has occurred.
Steps 603 and 604: These steps can be implemented using a variety of techniques, such as e-mail; conventional postal mail; via an electronic bill presentment system (e.g., the presentment part of a BPPS as described with regard to
Step 605: In some cases, intermediary (here, ad agency 504) is allowed to store the payment card account number issued to it by end-corporate 502 in a manner that complies with the standards promulgated by the PCI Security Standards Council, LLC, Wakefield, Mass. USA. In one non-limiting example, there is a PCI-compliant data store on a server 700 (see
Step 606: Consider the virtual card push of step 606. In some cases, the virtual card number is created by MasterCard's IN CONTROL or a similar product (generally, a virtual card number generation facility 810), using techniques such as those described in the herein-mentioned two Flitcroft patents. Ad agency 504 or a third party acting on its behalf contacts the virtual card number generation facility, requests a virtual card number, obtains the virtual card number in response, and pushes the virtual card number to the supplier. In a non-limiting example, this can be done via e-mail. In an alternative approach, media supplier 506 connects as a party to the above-discussed secure portal and retrieves the account information. In such cases, there may still be an e-mail to the supplier to advise the supplier that a virtual card number is waiting for them and they should go to the portal and retrieve it. Consider aspects of automation occurring from the time when the lodged card is “hit” to the time when the virtual card number is created. When the first card (lodged card) is “hit” by the ad agency, the ad agency will obtain an authorization (“auth”) number for that transaction. The return of that auth number triggers the workflow to generate the virtual card and the notification to the media supplier that a virtual card number payment is waiting for them. In some cases, the receipt of the “auth” number may not result in immediate virtual card creation. There may be additional intermediate steps such as approval, or the ad agency may need to make sure that the invoice that the media supplier gave them was reconciled, and so on. The creation of the “auth” nevertheless triggers that intermediate workflow, which is determined by the ad agency as appropriate. For example, the ad agency may want three steps; or they may pay as soon as their funds come in. One or more embodiments include reconciliation by the ad agency to make sure that it is meeting its sequential liability requirements.
In some cases, a work flow engine 808 resides on a server at agency 504 and the work flow is triggered by obtaining the “auth” number. Alternatively, the work flow engine can reside on a server of the card issuer 651 or in an alternative location. For example, the virtual card number generation facility may reside on a server of the operator of a payment card network and the workflow engine can also reside there. When the server does not reside at the ad agency 504, there may be a data interchange between the server and the ad agency. The work flow engine and interfaces may reside with a third party system; for example, in a cloud or software as a service environment. Thus, one or more embodiments are implemented by a party that is a third party to all three parties to the transaction(s) per se (i.e., end-corporate 502, ad agency 504, and media supplier 506). This third party can be, for example, one or more of the following:
The payment card network operator could provide a platform such as the MASTERCARD PURCHASE CONTROL® commercial payments solution (registered mark of MasterCard International Incorporated, Purchase, N.Y. US) or a similar platform. Non-limiting examples of third party service providers include ANCHOROPS, INC., Westborough, Mass., USA and CSI/CardPayment Solutions (Registered ISO of Wells Fargo Bank, N.A., Walnut Creek, Calif., US). These third party providers could provide, for example, alternative commercial payments solutions.
Further comments on Step 605: the card number for the lodged card could be stored by agency 504 or the aforementioned third party. Storage by the third party may be particularly suitable when the ad agency is not PCI-compliant. The generation of the virtual card number (VCN) may occur, for example, at a virtual card number generation facility such as an IN CONTROL server at MasterCard or the like. The work flow that is triggered once the auth number is returned for the “pull” may be carried out, for example, using a work flow engine that may, for example, be located at the aforementioned third party and be used by ad agency 504. Thus, in one or more embodiments, ad agency 504 securely accesses an application (“app”) provided by the operator of a payment card network or other third party (e.g., issuer 651).
Thus, to summarize, in one or more embodiments, a work flow engine 808 runs at a third party such as issuer 651 or the operator 2008 of a payment card network. Once the “auth” number is generated, it triggers the work flow engine 808. If all the correct conditions are satisfied, the work flow engine initiates step 606, “push” to media supplier 506. This push can include, for example, an e-mail with the VCN or an e-mail telling supplier 506 to log on securely to a portal where the supplier can obtain the VCN. In one or more embodiments, the portal is part of the third party system. The third party system 802, in one or more embodiments, advantageously includes and integrates a number of discrete applications.
Further Aspects of Step 606 and Settlement Steps 607-610: in some cases, settlement steps 607, 608, 609, and 610 are carried out using standard batch processing functionality in a payment card network such as BANKNET or the like. In some cases, the standard settlement process is modified to include special reference information passing through a payment card network such as BANKNET during the settlement process; for example, an invoice number or some other indication. Note that in some cases, the ad agency reconciliation as to the media supplier is based on the single use virtual account number employed in step 606. Employing a single use account is beneficial because it creates a one-to-one relationship and eases reconciliation on the back end. However, other approaches could be used in other embodiments. For example, some embodiments use straight-through processing via a dynamic account with the same number used repeatedly. In this context, a “dynamic account” means that the same account is used repeatedly, but that the issuer processor puts a control on the account that only opens the line of credit for a certain amount and for a certain period of time. In essence, this approach involves the use of velocity controls instead of issuing a new account number for each transaction. In a further alternative embodiment for step 606, instead of providing media supplier 506 with a virtual card number, the third party service has a card number of the media supplier 506 on file and uses a special transaction to put funds onto the card; this is somewhat analogous to an approach using a pre-paid card where the amount of the transaction is controlled. Thus:
Note that US Patent Application Publication 2010-0100480 A1 of Theresa Altman et al., expressly incorporated herein by reference in its entirety for all purposes, discloses an innovative technique for allowing users of an electronic payment bill payment system to pay billers using payment card accounts of the payors not the billers, by sending a non-financial message through the electronic payment bill payment system, including the card number of the payor's card; the biller then charges the payor's card in a conventional manner. In some circumstances, such techniques could be used to provide the agency or third party with the lodged card details of the corporate client 502 or to send the virtual card details to the supplier 506.
Also, note that wherever card numbers are supplied, other needed details such as expiration date and security code can also be supplied as appropriate. Furthermore, note that in one or more embodiments, at least some aspects of steps 605, 606, 607, 608, 609, and 610 can be carried out or otherwise facilitated with a payment card network.
A PNIP such as a MIP is typically located on the premises of the acquirer or issuer as seen in
Optional back end 806 may, in some instances, be responsive to the portal, and may obtain, for example, a communication wherein end corporate 502 directs ad agency 504 to initiate the pull payment of step 605. Portal 804 may securely serve out HTML code over Internet 816 to client computers at any of the parties to enable the communications described herein. Work flow engine 808 may include, for example, compiled or interpreted high-level code that implements the logic described elsewhere herein. Optionally, engine 808 is broken into pull engine 808-1 which implements the pull payment and push engine 808-2 which implements the push payment. Once the auth code for the pull payment is received, the push payment workflow may commence, automatically generating the push payment. External rating system interface 818 interfaces with external rating system 820. In the non-limiting example of media advertising purchases, system 820 is provided by, for example, Marketron, Inc.; Mediaocean; Advantage Software, Inc.; and/or Strata Marketing, Inc. Interface 818 can be, for example, suitable code that accesses an API exposed by the system 820. In other applications, other systems that verify compliance with an objective can be utilized.
In another aspect, instead of using a VCN, suitable gateway functionality is employed (the gateway such as the electronic transaction apparatus described in U.S. Pat. No. 8,732,044 of Lovelett, et al. is a non-limiting example of a suitable gateway). In this aspect, system 802 stores card account information for both pull and push payments and settles both streams of transactions by pushing transactions out of the system directly to the acquirers without manual intervention. In one or more embodiments, this provides a faster and more secure way to deliver account information directly to the banks of the payment recipients. One or more embodiments employ integration with acquirers, storing card account numbers for pull and push payments and sending account numbers directly to the acquirers without manual intervention. A suitable gateway facilitates direct integration with one or more acquirers.
In one or more embodiments, system 802 improves the functioning of purchasing system between end-corporate and the supplier.
It should be noted that in one or more embodiments, system 802 creates a unique identifier to link the transactions together (e.g., a trace number to link pull payment to push payment). In a non-limiting example, this is done by work flow engine 808 using logic apart from the pull and push engines.
Given the discussion thus far, it will be appreciated that, in general terms, one aspect of the invention includes a method for automating sequential electronic payments, in a scenario where a buyer 502 purchases at least one of goods and services from a seller 506 via an intermediary 504. One step includes obtaining, at the intermediary and/or a third party, an indication that payment to the intermediary from the buyer is appropriate.
In some instances, this step of obtaining an indication is carried out by buyer 502 indicating approval via portal 804 over a secure connection using Internet 816, with back end 806 advising the intermediary 504. The buyer can receive a notification from the system 802 indicating that an invoice is ready for approval; for example, upon reconciliation of the media purchase that is required as a condition before the payment is pulled. Once that happens, a system notification goes out to the buyer (end corporate) and the end corporate will then come in and trigger the payment for the payment to actually be released.
In some instances, this step of obtaining an indication is carried out via an auto-approval process. Once conditions are satisfied/reconciled around the purchase agreement for the media buy, the system 802 (in particular, the workflow engine 808) takes the card account on file and essentially sends a message directly to the acquirer to process the transaction and pull it through the system, hitting the card account and paying the merchant or the ad agency in, say, two days. Auto approval is preferred in at least some cases because it is faster. With regard to the workflow engine 808, the same may have additional functionality as described herein besides that in the (optional) pull and push engines. In one or more embodiments, the aspect of the system taking the card account on file and sending a message directly to the acquirer is carried out before the “pull.” In essence, the engine 808 undertakes a three-way match for the purchase request 601, invoice 603, and whatever indication (e.g., third party rating data from system 820) is relied on to confirm that the media purchase met expectations.
In some instances, this step of obtaining an indication involves the elapse of an appropriate amount of time from the invoice date without dispute (calculated, for example, by a timer or calendar function within system 802).
In some instances, this step of obtaining an indication involves the intermediary 504 self-certifying via portal 804.
It is worth noting as an aside that in one or more embodiments, the Buyer, Intermediary, and Media supplier all access system 802 via the same portal 804, with access controls specific to each user. Of course, two or more different portals could be used in other embodiments.
Now continuing with the description of the exemplary method, in a further step, responsive to the indication being obtained, the intermediary and/or the third party initiates a pull payment, via a payment card network (2008 is a non-limiting example), for an on-file payment card account number of the buyer. This step can be carried out, for example, by Work Flow Engine 808 in system 802 pulling the account number from data store 814 and sending it into network 2008 via payment card network interface 812. Where engine 808 is divided into pull engine 808-1 and push engine 808-2, this step can be performed with pull engine 808-1.
In a still further step, responsive to success of the pull payment, the intermediary and/or the third party initiates a push payment to the seller. One example of “success” is getting the “auth” number for the pull payment back from the acquirer via the payment card network and into the work flow engine 808. The auth number is provided from the acquirer back to system 802 over network 2008 or the like over interface 812. In at least some instances, the timing for generation and release (push) of the virtual card number can be configured and/or scheduled by the Agency to allow for review and reporting. Single or multi-use virtual card numbers can be employed. Controls on the virtual card can be set, for example, by the issuer or issuer processor. Again, optionally, engine 808 includes two work flows; 808-1 around the pull payment and 808-2 around the push payment. Receipt of the “auth” code links the two work flows; it closes out the pull payment and starts the push payment. exemplary push payment details are described elsewhere herein.
Again, as discussed above, references to a “Lodged Card solution” or “Virtual Card solution” are exemplary and non-limiting; in one or more embodiments, it is simply a credit card account issued to end-corporate for use specifically with Ad Agency (which has previously been referred to as Intermediary). Both are technically virtual card solutions in that no plastic is issued, just accounts. Also, as discussed above, the scenario could include one or two different card issuers—one for intermediary and one for end-corporate or same for both.
In some cases, the step of initiating the push payment includes the intermediary and/or the third party making a single-use virtual payment card number available to the seller. This number could be generated by VCN generator 810 and could be provided, for example, as discussed below.
In some instances, the intermediary and/or the third party makes the single-use virtual payment card number available to the seller by sending the single-use virtual payment card number to the seller by e-mail. For example, Engine 808 (optionally push engine 808-2) in system 802 sends e-mail over Internet 816.
In some instances, the intermediary and/or the third party makes the single-use virtual payment card number available to the seller by advising the seller to log onto a secure web portal. For example, Engine 808 (optionally push engine 808-2) in system 802 advises the seller to access Portal 804.
In some cases, the step of initiating the push payment includes the intermediary and/or the third party enabling the seller to make a limited charge against a reusable payment card account number. This step could be carried out, for example, with engine 808 (optionally push engine 808-2).
In some cases, the step of initiating the push payment includes the intermediary and/or the third party initiating a special payment transaction over the payment card network (e.g., 2008) wherein the seller has a payment card account in which the seller can receive payments via the special payment transaction over the payment card network. For example, Engine 808 (optionally push engine 808-2) sends into network 2008 via interface 812 an ISO-8583 message 0100 with Transaction Type (DE3sf1)=“28” (Payment Transaction) or an ISO-8583 message 0200 with Transaction Type (DE3sf1)=“28” (Payment Transaction).
In some cases, additional steps include issuing the on-file payment card account number to the buyer 502; providing a server of the intermediary and/or the third party with access to a virtual card number generator 810; provisioning the server of the intermediary 504 and/or the third party with software to enable the pull payment; and providing a server of the seller 506 with software to enable the push payment. Some embodiments may employ a cloud solution where little or no provisioning is required.
There are many different ways that an indication can be obtained that payment is appropriate; non-limiting examples include: (1) buyer goes on portal and approves, (2) auto-approval, (3) time lapse, and (4) self-certification by intermediary. One example of auto-approval is the case where the parties agree that for certain kinds of media, further certification is not needed. Furthermore in this regard, while online media has many potential discrepancies, in radio, it is much easier to confirm that an ad was aired. In some cases, payment might be made for radio spots five days after invoice receipt. In some cases, self-certification could involve linkage to an entity such as Mediaocean or another third party that verifies the number of impressions. Thus, auto-approval might in some instances be employed for non-critical types of media; where verification of the number of impressions is not believed to be required. In such cases, the mere fact the ad has been placed and aired is sufficient. In auto-approval, the: buyer sets up conditions with the system in accordance with their relationship with the agency; for example, for a simple spot purchase or below a certain monetary threshold, such that no audit is needed. This can also be implemented on a “by supplier” basis. In auto-approval, the trigger is the presentment of the invoice. In some cases, flagging is employed to flag for eligibility for auto-approval based on party eligibility. In another aspect, logic is provided to recognize a media buy as, for example, a radio buy or other buy that is eligible for reduced scrutiny.
In some cases, the obtaining, at the intermediary and/or the third party, of the indication that the payment to the intermediary from the buyer is appropriate, includes the buyer authorizing the payment to the intermediary from the buyer. For example, the buyer assents via a secure web portal 804 of the intermediary and/or the third party.
In some cases, the obtaining, at the intermediary and/or the third party, of the indication that the payment to the intermediary from the buyer is appropriate, includes at least obtaining an indication that an outside agency certifies that the at least one of goods and services meet a required standard. For example a rating agency certifies ad impressions.
As noted, in some cases, all parties use the same portal, and the parties may be provided with different access controls to the portal.
In some cases, the obtaining, at the intermediary and/or the third party, of the indication that the payment to the intermediary from the buyer is appropriate, includes elapse of a period of time previously agreed to by the intermediary and the buyer. This might be implemented, for example, via timer or calendar functionality on system 802.
In some cases, the obtaining, at the intermediary and/or the third party, of the indication that the payment to the intermediary from the buyer is appropriate, includes at least presentment of an associated invoice (or other suitable documentation) to end-corporate 502 in accordance with a prior agreement (i.e., prior agreement permits intermediary and/or third party to treat presentment of an associated invoice (or other suitable documentation) to end-corporate 502 as a “trigger.”
In some instances, notifications are frequently sent to parties, reminding them that they need to log in and approve the payment.
As noted elsewhere, on or more embodiments include provision of a system; the system includes distinct software modules, and each of the distinct software modules is embodied on a non-transitory computer-readable storage medium. In some cases, the distinct software modules include a portal module and a work flow engine module. In some cases, the distinct software modules include a timer-calendar module (e.g., time and date available in WINDOWS and other operating systems) and a work flow engine module. In some cases, the distinct software modules include an external rating system interface module and a work flow engine module.
In some instances, the buyer assents via the portal module executing on at least one hardware processor; the portal module executing on the at least one hardware processor forms at least a portion of the secure web portal. The intermediary and/or the third party initiates the pull payment and the push payment, at least in part, via the work flow engine module executing on the at least one hardware processor. In some embodiments, separate pull and push engines 808-1 and 808-2 are employed.
In some embodiments, the intermediary and/or the third party obtains the indication that payment is appropriate at least via obtaining an indication that an outside agency certifying that the at least one of goods and services meet a required standard. indication can be obtained, for example, by the external rating system interface module executing on at least one hardware processor; and the intermediary and/or the third party initiate the pull payment and the push payment via the work flow engine module executing on the at least one hardware processor. Again, in some embodiments, separate pull and push engines 808-1 and 808-2 are employed.
In some cases, the intermediary and/or the third party obtains the indication that payment is appropriate via elapse of a period of time previously agreed to by the intermediary and the buyer. The obtaining of the indication that the payment is appropriate includes the elapse of the period of time being calculated by the timer-calendar module executing on at least one hardware processor; and the intermediary and/or the third party initiates the pull payment and the push payment via the work flow engine module executing on the at least one hardware processor. Again, in some embodiments, separate pull and push engines 808-1 and 808-2 are employed.
In some cases, the intermediary and/or the third party obtains the indication that payment is appropriate via presentment of an associated invoice (or similar documentation) in accordance with a prior agreement. The obtaining of the indication that the payment is appropriate includes, for example, invoice presentment (or similar documentation) implemented using a variety of techniques, such as e-mail; conventional postal mail; via an electronic bill presentment system (e.g., the presentment part of a BPPS as described with regard to
It should be noted that
As noted, in some instances, the “push” is implemented in the form of a notification to the media supplier to run a transaction through their acquirer. In an alternative approach, payment is pushed to the acquirer of the media supplier instead of pushing notification and having media supplier use their point-of-sale (POS) device to initiate the transaction.
In one or more embodiments, push payments can be carried out using gateway functionality such as the electronic transaction apparatus described in U.S. Pat. No. 8,732,044 of Lovelett, et al.—this is a non-limiting example of a suitable gateway.
In still another aspect, an apparatus for automating sequential electronic payments, in a scenario where a buyer purchases at least one of goods and services from a seller via an intermediary, includes means for carrying out the method steps of any of the methods described herein.
In a further aspect, an article of manufacture includes a computer program product for automating sequential electronic payments, in a scenario where a buyer purchases at least one of goods and services from a seller via an intermediary. The computer program product includes a tangible computer-readable recordable storage medium, storing in a non-transitory manner computer readable program code. The computer readable program code includes computer readable program code configured to cause the processor to carry out any one, some or all of the method steps herein (e.g., the instructions are loaded into the memory to configure the processor).
In an even further aspect, an apparatus for automating sequential electronic payments, in a scenario where a buyer purchases at least one of goods and services from a seller via an intermediary, includes a memory; at least one processor operatively coupled to the memory; and a persistent storage device operatively coupled to the memory and storing in a non-transitory manner instructions which when loaded into the memory cause the at least one processor to be operative to carry out any one, some or all of the method steps herein. In at least some instances, the instructions on the persistent storage device include distinct software modules as described herein.
The modules can include, for example, a work flow engine module. In some cases, the work flow engine module resides on a server of the intermediary and the at least one processor is a processor of the server. However, the work flow engine module could also reside elsewhere; e.g., a card issuer (either a common card issuer that issues cards for both the intermediary 504 and for end-corporate 502 or an issuer for either one in the case when there are separate issuers).
Embodiments of the invention can employ hardware and/or hardware and software aspects. Software includes but is not limited to firmware, resident software, microcode, etc.
Software might be employed, for example, in connection with one or more of modules to implement at least a portion of one or more of the elements of system 802; a terminal 122, 124, 125, 126; a reader 132; a host, server, and/or processing center 140, 142, 144 (optionally with data warehouse 154) of a merchant, issuer, acquirer, processor, other third party described herein, entity described in connection with
As is known in the art, part or all of one or more aspects of the methods and apparatus discussed herein may be distributed as an article of manufacture that itself comprises a tangible computer readable recordable storage medium having computer readable code means embodied thereon. The computer readable program code means is operable, in conjunction with a computer system, to carry out all or some of the steps to perform the methods or create the apparatuses discussed herein. A computer-usable medium may, in general, be a recordable medium (e.g., floppy disks, hard drives, compact disks, EEPROMs, or memory cards) or may be a transmission medium (e.g., a network comprising fiber-optics, the world-wide web, cables, or a wireless channel using time-division multiple access, code-division multiple access, or other radio-frequency channel). Any medium known or developed that can store information suitable for use with a computer system may be used. The computer-readable code means is any mechanism for allowing a computer to read instructions and data, such as magnetic variations on a magnetic medium or height variations on the surface of a compact disk. The medium can be distributed on multiple physical devices (or over multiple networks). For example, one device could be a physical memory media associated with a terminal and another device could be a physical memory media associated with a processing center. As used herein, a tangible computer-readable recordable storage medium is defined to encompass a recordable medium (non-transitory storage), examples of which are set forth above, but does not encompass a transmission medium or disembodied signal.
The computer systems and servers described herein each contain a memory that will configure associated processors to implement the methods, steps, and functions disclosed herein. Such methods, steps, and functions can be carried out, by way of example and not limitation, by processing capability on one, some, or all of elements 122, 124, 125, 126, 140, 142, 144, 2004, 2006, 2008, 2010; on a computer implementing system 802; on processors of hosts and/or servers of other parties described herein; on a computer implementing functionality as in
Thus, elements of one or more embodiments of the invention, such as, for example, 122, 124, 125, 126, 140, 142, 144, 2004, 2006, 2008, 2010; a computer implementing 802 and its components; on processors of hosts and/or servers of other parties described herein; functionality in
Accordingly, it will be appreciated that one or more embodiments of the invention can include a computer program comprising computer program code means adapted to perform one or all of the steps of any methods or claims set forth herein when such program is run on a computer, and that such program may be embodied on a computer readable medium. Further, one or more embodiments of the present invention can include a computer comprising code adapted to cause the computer to carry out one or more steps of methods or claims set forth herein, together with one or more apparatus elements or features as depicted and described herein.
As used herein, including the claims, a “server” includes a physical data processing system (for example, system 700 as shown in
Furthermore, it should be noted that any of the methods described herein can include an additional step of providing a system comprising distinct software modules embodied on one or more tangible computer readable storage media. All the modules (or any subset thereof) can be on the same medium, or each can be on a different medium, for example. The modules can include any or all of the components shown in the figures. Referring again to
Thus, aspects of the invention can be implemented, for example, by one or more appropriately programmed general purpose computers, such as, for example, servers, mobile devices, or personal computers, located at one or more of the entities in the figures, as well as within the payment network 2008 and/or payment system 1006. Such computers can be interconnected, for example, by one or more of payment network 2008, another VPN, the Internet, a local area and/or wide area network (LAN and/or WAN), via an EDI layer, and so on. Note that element 2008 represents both the network and its operator. The computers can be programmed, for example, in compiled, interpreted, object-oriented, assembly, and/or machine languages, for example, one or more of C, C++, Java, Visual Basic, COBOL, Assembler, Structured Query Language (SQL), and the like (an exemplary and non-limiting list), and can also make use of, for example, Extensible Markup Language (XML), known application programs such as relational database applications (e.g., IBM DB2® software available from International Business Machines Corporation, Armonk, N.Y., US; SAS® software available from SAS Institute, Inc., Cary, N.C., US), spreadsheets (e.g., MICROSOFT EXCEL® software available from Microsoft Corporation, Redmond, Wash., US), and the like. The computers can be programmed to implement the logic and/or data flow depicted in the figures. In some instances, messaging and the like may be in accordance with the International Organization for Standardization (ISO) Specification 8583 Financial transaction card originated messages—Interchange message specifications and/or the ISO 20022 or UNIFI Standard for Financial Services Messaging, also incorporated herein by reference in its entirety for all purposes. In one or more embodiments, some messages may be in accordance with NACHA Automated Clearing House (ACH) rules and regulations.
Although illustrative embodiments of the invention have been described herein with reference to the accompanying drawings, it is to be understood that the invention is not limited to those precise embodiments, and that various other changes and modifications may be made by one skilled in the art without departing from the scope or spirit of the invention.
This patent application claims the benefit of U.S. Provisional Patent Application Ser. No. 62/030,479 filed on 29 Jul. 2014 and entitled “APPARATUS, METHOD, AND COMPUTER PROGRAM PRODUCT FOR AUTOMATED SEQUENTIAL ELECTRONIC PAYMENTS.” The complete disclosure of the aforementioned U.S. Provisional Patent Application Ser. No. 62/030,479 including all appendices thereof is expressly incorporated herein by reference in its entirety for all purposes.
| Number | Date | Country | |
|---|---|---|---|
| 62030479 | Jul 2014 | US |
