A method for completing a transaction includes: a backend server connected to a communication network executes an application backend of a transaction application; a first terminal device connected to the communication network via a first connection executes a first application frontend of the transaction application; the first application frontend transmits a transaction request indicating the transaction to be started and a second application frontend and comprising transaction data associated with the indicated transaction to the application backend via the first connection; a second terminal device connected to the communication network via a second connection executes the second application frontend of the transaction application; the application backend transmits an authorization request to the second application frontend via the second connection; the second application frontend authorizes the requested transaction and transmits a transaction authorization to the application backend via the second connection; and the application backend completes the transaction.

A method for operating a mobile Point-of-Sales (mPOS) application for executing a transaction includes: a Universal Integrated Circuit Card (UICC) card connected to a terminal device executes in interaction with the terminal device an application frontend of the mPOS application that provides, upon launch, an I/O interface with a human machine interface displayed by a touchscreen of the terminal device and a machine-to-machine interface; and the application frontend, for starting a transaction, captures transaction data associated with the transaction to be started via the human machine interface, reads further transaction data via the machine-to-machine interface from a transaction device separate from the terminal device and arranged close to the terminal device, generates a transaction authorization authorizing the requested transaction, and transmits the transaction authorization, the transaction data and the further transaction data via a connection to a remote backend server for completing the transaction.

A computer-based method for communicating liability acceptance for payment card transactions is provided. The method uses a computer device including a processor and a memory. The method includes receiving, by the processor, a transaction authorization request message for a payment card transaction having a default-liable party. The transaction authorization request message includes a shifted-liability acceptance indicator identifying a different party to the transaction that accepts liability for the payment card transaction. The method also includes authorizing the payment card transaction based at least in part on the shifted-liability acceptance indicator. The shifted-liability acceptance indicator changes the liability for the payment card transaction from the default-liable party to the different party accepting liability.

A computer-based method for communicating liability acceptance for payment card transactions is provided. The method uses a computer device including a processor and a memory. The method includes receiving, by the processor, a transaction authorization request message for a payment card transaction having a default-liable party. The transaction authorization request message includes a shifted-liability acceptance indicator identifying a different party to the transaction that accepts liability for the payment card transaction. The method also includes authorizing the payment card transaction based at least in part on the shifted-liability acceptance indicator. The shifted-liability acceptance indicator changes the liability for the payment card transaction from the default-liable party to the different party accepting liability.

Aspects described herein may relate to a transaction exchange platform using a streaming data platform (SDP) and microservices to process transactions according to review and approval workflows. The transaction exchange platform may receive transactions from origination sources, which may be added to the SDP as transaction objects. As the transactions are processed, the transactions may require access to a resource (e.g., a key value in a database). A microservice processing the transaction may request, from a locking microservice, a lock for the resource. The locking microservice may query a local cache to determine whether a lock exists for the resource. If the local cache determines that no lock exists for resource, the locking mechanism may employ a consensus protocol to obtain a lock for the resource from a plurality of clusters. If consensus is reached, a lock for the resource may be granted to the requesting microservice.

Aspects described herein may relate to a transaction exchange platform using a streaming data platform (SDP) and microservices to process transactions according to review and approval workflows. The transaction exchange platform may receive transactions from origination sources, which may be added to the SDP as transaction objects. As the transactions are processed, the transactions may require access to a resource (e.g., a key value in a database). A microservice processing the transaction may request, from a locking microservice, a lock for the resource. The locking microservice may query a local cache to determine whether a lock exists for the resource. If the local cache determines that no lock exists for resource, the locking mechanism may employ a consensus protocol to obtain a lock for the resource from a plurality of clusters. If consensus is reached, a lock for the resource may be granted to the requesting microservice.

Systems and methods for motion-enabled transactions are disclosed. The system may allow users to complete transactions with merchants via an air sign input. The system may receive a motion-enabled transaction request comprising an air sign input. The system may determine a stored air sign symbol based on the air sign input. The system may retrieve a merchant identifier, a transaction type, and a transaction cost based on the determined stored air sign symbol. The system may transmit a transaction confirmation comprising the merchant identifier, the transaction type, and the transaction cost. In response to the user confirming the transaction confirmation, the system may authorize and process the transaction.

Systems and methods for motion-enabled transactions are disclosed. The system may allow users to complete transactions with merchants via an air sign input. The system may receive a motion-enabled transaction request comprising an air sign input. The system may determine a stored air sign symbol based on the air sign input. The system may retrieve a merchant identifier, a transaction type, and a transaction cost based on the determined stored air sign symbol. The system may transmit a transaction confirmation comprising the merchant identifier, the transaction type, and the transaction cost. In response to the user confirming the transaction confirmation, the system may authorize and process the transaction.

A security authentication system for a website provides a safe login without having to directly enter an ID and a password on a user device requesting login to the website. A first user device receives one-time use authentication information from a second user device after the second user device received the one-time use authentication information from an authentication server without the authentication server receiving user login authentication information from the second user device. A request is transmitted to the authentication server based on the one-time use authentication information and the user login authentication information. In response to the request, one-time password (OTP) information is received from the authentication server. The OTP information is presented by the first user device, such that the OTP information can be entered into the second user device and used in a request to log in to the website.

Aspects described herein may relate to a transaction exchange platform using a streaming data platform (SDP) and microservices to process transactions according to review and approval workflows. The transaction exchange platform may receive transactions from origination sources, which may be added to the SDP as transaction objects. Microservices on the transaction exchange platform may interact with the transaction objects based on configured workflows associated with the transactions. Processing on the transaction exchange platform may facilitate clearing and settlement of transactions. Some aspects may provide for dynamic and flexible reconfiguration of workflows and/or microservices. Other aspects may provide for data snapshots and workflow tracking, allowing for monitoring, quality control, and auditability of transactions on the transaction exchange platform.