DOWNLOADABLE MIDDLEWARE ACH

Brand Owner Address Description
BRIDGELINK PAYNATION 9891 Irvine Center Drive, Suite 200 Irvine CA 92618 Downloadable middleware for ACH, electronic funds transfer, electronic payments, electronic check, credit card transaction, authorization, factoring, and payment processing services for mobile applications, website, e-commerce, payment gateways, hosted payment pages, credit card terminals, and application programming interface (API);BRIDGE LINK;Charge card and credit card payment processing services; Credit card authorization services; Credit card factoring services; Credit card payment processing services; Credit card transaction processing services; Credit card transaction processing services provided via mobile applications, website, e-commerce, payment gateways, hosted payment pages, credit card terminals, and application programming interface (API); Processing of credit card payments; Providing electronic processing of electronic funds transfer, ACH, credit card, debit card, electronic check and electronic payments; Providing electronic processing of ACH and credit card transactions and electronic payments via a global computer network;Application service provider (ASP) featuring e-commerce software for use as a payment gateway that authorizes processing of credit cards or direct payments for merchants;
 

Where the owner name is not linked, that owner no longer owns the brand

    
Technical Examples
  1. The present invention, known as the Middleware Brokering System, brokers messages between middleware computing products. Each middleware service can send data to the Middleware Brokering System in its native data format and programming syntax. The Middleware Brokering System converts the data transmitted from the different platforms into a standard format known as a structured event. Messages are then transmitted to and stored in an underlying, commercially available publish/subscribe engine. The Middleware Brokering System contains internal logic that determines whether any subscribers are interested in the messages. If an interested subscriber is found, the Middleware Brokering System retrieves the message from the publish/subscribe engine, converts the data from the structured event into the native format of the receiving application, and sends the message to the appropriate application.