Phil Kumnick - Phoenix AZ, US Krishna Koganti - Cupertino CA, US Davidson Wuichet - San Mateo CA, US Lloyd Cato - Sunnyvale CA, US Jeff Kusheba - Litchfield Park AZ, US
International Classification:
G06Q 20/40
US Classification:
705 44
Abstract:
Embodiments of the invention are directed to passing a plurality of communications directly from a merchant to a payment processing network. A first communication may include payment information in an authorization request, while a second transaction may include non-payment transaction data. The communications may be linked with a transaction identifier. In other embodiments, a capture file process is disclosed where capture files are generated by the payment processing network, and transactions are subsequently cleared and settled.
Phil Kumnick - Phoenix AZ, US Krishna Koganti - Cupertino CA, US Davidson Wuichet - San Mateo CA, US Lloyd Cato - Sunnyvale CA, US Jeff Kusheba - Litchfield Park AZ, US
International Classification:
G06Q 20/40 G06Q 30/02 G06Q 20/20 G06Q 20/38
Abstract:
Embodiments of the invention are directed to passing a plurality of communications directly from a merchant to a payment processing network. A first communication may include payment information in an authorization request, while a second transaction may include non-payment transaction data. The communications may be linked with a transaction identifier. In other embodiments, a capture file process is disclosed where capture files are generated by the payment processing network, and transactions are subsequently cleared and settled.
Phil Kumnick - Phoenix AZ, US Krishna Koganti - Cupertino CA, US Davidson Wuichet - San Mateo CA, US Lloyd Cato - Sunnyvale CA, US Jeff Kusheba - Litchfield Park AZ, US
International Classification:
G06Q 20/40 G06Q 30/02
US Classification:
705 1423, 705 44
Abstract:
Embodiments of the invention are directed to passing a plurality of communications directly from a merchant to a payment processing network. A first communication may include payment information in an authorization request, while a second transaction may include non-payment transaction data. The communications may be linked with a transaction identifier. In other embodiments, a capture file process is disclosed where capture files are generated by the payment processing network, and transactions are subsequently cleared and settled.