Direct Data Share

A data share computing device configured to supplement payment authorization information, received from a payment processing service, corresponding to a financial transaction between a user and a merchant, the data share computing device comprising:

• one or more processors, and
• memory storing instructions that, when executed by one or more processors, cause the data share computing device to:
• receive, from a second computing device and via a first application programming interface (API), supplemental transaction metadata comprising one or more data elements corresponding to one or more attributes of the financial transaction, wherein the supplemental transaction metadata is associated with a concurrent transmission of basic payment information, for the financial transaction, by the second computing device to the payment processing service, wherein the data elements are supplemental to the basic payment information sent to the payment processing service according to a pre-existing standard;
• validate, based on a predicted processing time associated with processing, by the payment processing service, of the basic payment information, the supplemental transaction metadata based on one or more criteria, wherein validating the supplemental transaction metadata comprises at least validating a first data element of the supplemental transaction metadata, and wherein the one or more criteria are associated with one or more of:
• validity, consistency, or formatting of data elements of the supplemental transaction metadata;
• receive, from the payment processing service and via a second interface different from the first API, payment authorization information corresponding to the financial transaction, wherein the payment authorization information indicates whether the basic payment information, transmitted by the second computing device to the payment processing service, caused the financial transaction to be approved by the payment processing service, and wherein validating the supplemental transaction metadata received from the second computing device is performed prior to receiving the payment authorization information from the payment processing service;
• match the validated supplemental transaction metadata for the financial transaction received from the second computing device with the payment authorization information received from the payment processing service for the financial transaction;
• determine an authorization result indicating whether the financial transaction is authorized based on the payment authorization information and the supplemental transaction metadata;
• and
• send, to the merchant and based on an authorization timing requirement associated with the financial transaction and the payment processing service, the authorization result.

One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause a data share computing device to supplement payment authorization information, received from a payment processing service, corresponding to a financial transaction between a user and a merchant by causing the data share computing device to:

• receive, from a second computing device and via a first application programming interface (API), supplemental transaction metadata comprising one or more data elements corresponding to one or more attributes of the financial transaction, wherein the supplemental transaction metadata is associated with a concurrent transmission of basic payment information, for the financial transaction, by the second computing device to the payment processing service, wherein the data elements are supplemental to the basic payment information sent to the payment processing service according to a pre-existing standard;
• validate, based on a predicted processing time associated with processing, by the payment processing service, of the basic payment information, the supplemental transaction metadata based on one or more criteria, wherein validating the supplemental transaction metadata comprises at least validating a first data element of the supplemental transaction metadata, and wherein the one or more criteria are associated with one or more of:
• validity, consistency, or formatting of data elements of the supplemental transaction metadata;
• receive, from the payment processing service and via a second interface different from the first API, payment authorization information corresponding to the financial transaction, wherein the payment authorization information indicates whether the basic payment information, transmitted by the second computing device to the payment processing service, caused the financial transaction to be approved by the payment processing service, and wherein validating the supplemental transaction metadata received from the second computing device is performed prior to receiving the payment authorization information from the payment processing service;
• match the validated supplemental transaction metadata for the financial transaction received from the second computing device with the payment authorization information received from the payment processing service for the financial transaction;
• determine an authorization result indicating whether the financial transaction is authorized based on the payment authorization information and the supplemental transaction metadata;
• and
• send, to the merchant and based on an authorization timing requirement associated with the financial transaction and the payment processing service, the authorization result.