Abstract: A method for secure document exchange includes receiving a request from a content owner to initiate a document request of particular information from a record provider to a service provider; sending to the record provider a request for documentation, the request comprising at least: the particular information for the record provider to send to the service provider; contact information of the service provider to receive the particular information; and an encryption key with which to encrypt particular information; and sending to the service provider a notification message, the notification message comprising at least a decryption key with which to decrypt the particular information from the record provider.

Abstract: A system and method for secure and intuitive payment transactions at an ecommerce merchant website with a client device. The system has a trusted platform that hosts a Mediator site and Manifest database that includes a plurality of Manifest files. Each Manifest file includes a unique identifier and mapped payor information for a payment entity. The platform uses the Manifest to validate trusted payment entities and provide the Mediator site. The Mediator site generates cookies with payor information from the Manifest files, which are transmitted stored on user devices. These cookies are employed to facilitate trusted and intuitive transactions at merchant websites using dynamic interface objects presented on the user's client device interface.

Abstract: A payment card account system transaction request is received. The request was initiated by acceptance of a payment card account transaction by a merchant. The request includes a transaction amount. It is determined whether the merchant has selected EFT (electronic funds transfer) settlement for the payment card account transaction that the merchant accepted. In response to the receiving step and also in response to a result of the determination as to whether EFT settlement was selected, an EFT transaction request is routed for the transaction amount to an EFT system to benefit the merchant.

Abstract: A system and method for secure and intuitive payment transactions at an ecommerce merchant website with a client device. The system has a trusted platform that hosts a Mediator site and Manifest database that includes a plurality of Manifest files. Each Manifest file includes a unique identifier and mapped payor information for a payment entity. The platform uses the Manifest to validate trusted payment entities and provide the Mediator site. The Mediator site generates cookies with payor information from the Manifest files, which are transmitted stored on user devices. These cookies are employed to facilitate trusted and intuitive transactions at merchant websites using dynamic interface objects presented on the user's client device interface.

Abstract: A request for payment message is received. The message includes transaction data. A transaction identifier is generated. The transaction data is stored in association with the transaction identifier. The transaction identifier is transmitted to an acquirer bank. A request to retrieve data is received from a payer's bank. The request to retrieve data includes the transaction identifier. At least some of the transaction data is transmitted to the payer's bank. A confirmation is received from the payer's bank. The confirmation indicates that a real-time payment has been made in accordance with the request for payment message.

Abstract: Methods and apparatus for generating a secure QR code for use in a purchase transaction. In an embodiment, a directory service computer verifies the identity of a merchant by matching an acquirer financial institution (FI)-signed certificate and a stored certificate, wherein the acquirer FI-signed certificate was received from a merchant device along with a secure QR code request. The directory service computer then establishes an encrypted and Pinned SSL tunnel with the merchant device, receives a transaction message including a transaction amount, a universal unique identifier (UUID), and a transaction identifier (ID), updates an application transaction count (ATC) associated with the merchant, and generates and stores a secure one-way Hash value, generated by using a merchant identifier (ID), the transaction amount, the ATC, the UUID, and the transaction ID.

Abstract: A real-time payment system transaction is initiated to settle a purchase of goods or services. An indication is received that the real-time payment system transaction failed. In response to the indication, the purchase of goods or services is settled via a settlement system associated with a payment card account system.

Abstract: A method includes receiving an invoice token from a merchant, where the invoice token represents an invoice for an e-commerce transaction. The invoice token is transmitted to a payment services computer to request details of the invoice. The requested invoice details are received from the payment service computer, and an account is selected to support payment for the transaction. A payment transaction is initiated to settle the e-commerce transaction based on the invoice details and the account that was selected to support the payment.

Abstract: A method includes receiving a request for payment credentials. The request indicates an account from which payment for a transaction is to be made. A payment token is looked-up that corresponds to the indicated account. Dynamic expiry data and a dynamic token verification code are generated. As a response to the request, the looked-up payment token, the generated dynamic expiry data and the generated dynamic token verification code are transmitted.

Abstract: A method includes receiving a first ACH (automated clearing house) transaction at a local (domestic) sponsor bank. The first ACH transaction originates from a domestic originating bank. In response to the first ACH transaction, a second ACH transaction is executed from the local sponsor bank to a foreign sponsor bank. The second ACH transaction includes addressing messaging. The addressing messaging indicates a receiving bank in the same country as the foreign sponsor bank. The receiving bank is designated to receive a third ACH transaction from the foreign sponsor bank to benefit a recipient's account at the receiving bank. The addressing messaging contains an account number to identify the recipient's account.

Abstract: Methods and apparatus for generating a secure QR code for use in a purchase transaction. In an embodiment, a directory service computer verifies the identity of a merchant by matching an acquirer financial institution (FI)-signed certificate and a stored certificate, wherein the acquirer FI-signed certificate was received from a merchant device along with a secure QR code request. The directory service computer then establishes an encrypted and Pinned SSL tunnel with the merchant device, receives a transaction message including a transaction amount, a universal unique identifier (UUID), and a transaction identifier (ID), updates an application transaction count (ATC) associated with the merchant, and generates and stores a secure one-way Hash value, generated by using a merchant identifier (ID), the transaction amount, the ATC, the UUID, and the transaction ID.

Abstract: Methods and apparatus for generating a secure QR code. In an embodiment, a directory service computer receives a secure QR code request from a merchant device that includes an acquirer financial institution (FI)-signed certificate. The directory service computer verifies the identity of a merchant, identifies a merchant identifier (ID), establishes an encrypted and Pinned SSL tunnel with the merchant device, and receives via the encrypted and Pinned SSL tunnel from the merchant device, a transaction message including a transaction amount, a universal unique identifier (UUID), and a transaction identifier (ID). The directory service computer then generates a Hash value, generates a dynamic secure QR code by combining the Hash value, the transaction ID and the merchant ID, and transmits the dynamic secure QR code data to the merchant device to conduct a purchase transaction.

Abstract: Methods and apparatus for generating a secure QR code. In an embodiment, a directory service computer receives a secure QR code request from a merchant device that includes an acquirer financial institution (FI)-signed certificate. The directory service computer verifies the identity of a merchant, identifies a merchant identifier (ID), establishes an encrypted and Pinned SSL tunnel with the merchant device, and receives via the encrypted and Pinned SSL tunnel from the merchant device, a transaction message including a transaction amount, a universal unique identifier (UUID), and a transaction identifier (ID). The directory service computer then generates a Hash value, generates a dynamic secure QR code by combining the Hash value, the transaction ID and the merchant ID, and transmits the dynamic secure QR code data to the merchant device to conduct a purchase transaction.

Abstract: Systems and methods are provided for systems and methods are described herein for providing a payment network platform that facilitates the integration of third-party value added service provider applications (“VAS Apps”) within the infrastructure of a payment device network. The systems and methods for providing a payment network platform described herein enable a series of operations whereby VAS Apps are selectively and under the control of the payment network platform system server, provided access to transaction data for transactions being processed by and through the payment device network system for the purpose of performing supplemental processing of such transactions and thereby providing value added services to transacting network participants that have subscribed to the services provided by the VAS App.

Abstract: A transaction request is received. The transaction request includes a merchant identifier. The merchant identifier is for identifying a merchant. The merchant's banking details are appended to the transaction request. The transaction request, with the appended banking details, is transmitted to a user's bank. Confirmation is received that a transaction has been performed in accordance with the transaction request. A confirmation is transmitted to the merchant to indicate that the transaction has been performed.

Abstract: A request for payment is received from a payment recipient. The request includes (a) invoice details and a transaction amount for a transaction between the payment recipient and a buyer; (b) identification of the payment recipient; and (c) an identifier that identifies the buyer. Payment recipient account information and buyer account information is appended to the request for payment. The payment recipient account information identifies the payment recipient's bank and bank account. The buyer account information identifies the buyer's bank and bank account. The request for payment is transmitted, including at least a portion of the payment recipient and buyer account information. A confirmation is received that the request for payment has been executed.

Abstract: A transaction authorization request message is received. The message includes a payment token and a merchant identifier. The payment token is detokenized to detect account mapping for the payment token. From the account mapping, it is determined that a debit transaction option and an ACH (automated clearing house) transaction option exist for the payment token. A selection is made between the debit transaction option and the ACH transaction option based at least in part on the merchant identifier.

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.

Abstract: A method of routing a payment transaction includes receiving a transaction request message. The message includes a payment token that was previously issued to an account holder. The payment token is translated into a funding account indicator. The funding account indicator is in a format defined for payment card account numbers in a payment account system. The funding account indicator is translated into a bank account number. The bank account number identifies a bank deposit account owned by the account holder. An EFT message is transmitted to initiate an EFT transaction to be funded from the bank deposit account owned by the account holder. The EFT message includes the bank account number.

Abstract: A method includes receiving a funds transfer request. The request includes an alias character string. The request is for requesting a funds transfer. The alias character string is translated to payment routing information. The payment routing information specifies a recipient's financial institution deposit account. The funds request is routed via a payment network for the purpose of being credited to the specified deposit account.