The disclosure relates to non-blocking messaging in an electronic trading venue (ETV) in which a matching engine sends groups of price-compatible contra-orders to a credit engine. Doing so may improve the ETV's efficacy and performance by eliminating the need for multiple roundtrips of messages in the case of a failed credit check, and/or by allowing the ETV to more faithfully implement its matching rules. Upon sending an order to the credit engine the matching engine marks it as ‘uncertain’ to indicate that additional requests received on it (e.g., cancels) must also be forwarded to the credit engine. When all pending requests on an order have been acknowledged by the credit engine the matching engine unmarks it as such. In addition to credit checking the credit engine may also perform computations related to advanced order types (e.g., icebergs) indicating the output of such in its acknowledgements to the matching engine.

Provided are a payment method and system through generation of a one-time payment-only number of a real card linked with an application, wherein in order to make payment safely by generating a one-time payment-only number every payment without leaving card information of a user in a provider's payment terminal or by using the generated one-time payment-only number, when a real card is linked with an application installed on a user terminal and the payment terminal recognizes the real card, a user signature input window, and transaction information about payment performed with a one-time payment-only number generated by a card company server are displayed on a screen of the application of the user terminal, and payment is performed when a signature of the user is input to the signature input window.

Provided are a payment method and system through generation of a one-time payment-only number of a real card linked with an application, wherein in order to make payment safely by generating a one-time payment-only number every payment without leaving card information of a user in a provider's payment terminal or by using the generated one-time payment-only number, when a real card is linked with an application installed on a user terminal and the payment terminal recognizes the real card, a user signature input window, and transaction information about payment performed with a one-time payment-only number generated by a card company server are displayed on a screen of the application of the user terminal, and payment is performed when a signature of the user is input to the signature input window.

A method, apparatus, and computer program product for alternative payment transactions are provided. An example computer-implemented method includes receiving a first request for payment associated with a first transaction that includes one or more first payment parameters and generating an initial payment responsive to the first request for payment based upon the first payment parameters. The computer-implemented method also includes determining first alternative payment data based upon first payment attribute data of a first user associated with the first transaction. The first payment attribute data is associated with non-cash liquid assets of the first user. The computer-implemented method additionally includes modifying the initial payment based upon the first alternative payment data and effectuating the modified initial payment from a first user account associated with the first user in satisfaction of the first transaction. The computer-implemented method may subsequently include modifying the first payment attribute data of the first user.

A method, apparatus, and computer program product for alternative payment transactions are provided. An example computer-implemented method includes receiving a first request for payment associated with a first transaction that includes one or more first payment parameters and generating an initial payment responsive to the first request for payment based upon the first payment parameters. The computer-implemented method also includes determining first alternative payment data based upon first payment attribute data of a first user associated with the first transaction. The first payment attribute data is associated with non-cash liquid assets of the first user. The computer-implemented method additionally includes modifying the initial payment based upon the first alternative payment data and effectuating the modified initial payment from a first user account associated with the first user in satisfaction of the first transaction. The computer-implemented method may subsequently include modifying the first payment attribute data of the first user.

A cryptocurrency secured by one or more loans is disclosed. The cryptocurrency is associated with one or more loans and the loan payments are distributed to the owner of the cryptocurrency. An identification of a pool of one or more bundled loans is received, and an indication of payments of the one or more bundled loans in the pool is be received. User information associated with a cryptocurrency exchange may be received, and the cryptocurrency is associated with the pool of one or more bundled loans. Transfer is made, to a user, of an amount of the payments of the one or more bundled loans in the pool.

To conduct a payment transaction at a merchant's point of sale using a mobile device, the mobile device initiates an authenticated communication session with a payment agent. The payment agent is an entity responsible for facilitating a payment transaction between the merchant and purchaser via their respective financial institutions. During the authenticated communication session, response to an input indicating the user of the mobile device wishes to make a payment, the mobile device generates a unique payment key that is based on at least one unique data of the mobile device. The mobile device transmits the payment key to the payment agent, and then transfers a copy of the payment key to the point of sale system. The merchant's payment system that transmits the payment key to the payment agent in a transaction request. The payment agent then verifies that the received payment key is the same as they received from the mobile device, and that the authenticated communication session is still valid, and then approves the transaction.

To conduct a payment transaction at a merchant's point of sale using a mobile device, the mobile device initiates an authenticated communication session with a payment agent. The payment agent is an entity responsible for facilitating a payment transaction between the merchant and purchaser via their respective financial institutions. During the authenticated communication session, response to an input indicating the user of the mobile device wishes to make a payment, the mobile device generates a unique payment key that is based on at least one unique data of the mobile device. The mobile device transmits the payment key to the payment agent, and then transfers a copy of the payment key to the point of sale system. The merchant's payment system that transmits the payment key to the payment agent in a transaction request. The payment agent then verifies that the received payment key is the same as they received from the mobile device, and that the authenticated communication session is still valid, and then approves the transaction.

In some implementations, a credit decision platform may receive a credit request from an applicant and obtain domestic historical data associated with the applicant from a credit bureau device. The credit decision platform may obtain access to an email account associated with the applicant based on determining that the domestic historical data associated with the applicant is insufficient to process the credit request. The credit decision platform may identify, using one or more machine learning models, a set of email messages included in the email account that are relevant to the credit request and may analyze content included in the set of email messages to generate non-domestic historical data associated with the applicant. The credit decision platform may generate a decision on the credit request based on an estimated creditworthiness of the applicant, which may be determined based on the non-domestic historical data.

Systems, methods, and computer program products are provided for validating a deposit request. The method includes receiving a deposit request from a user device. The deposit request includes a deposit transaction information relating to an intended deposit. The method also includes determining a deposit transaction confidence level based on the deposit transaction information. The deposit transaction confidence level indicates a likelihood of the intended deposit being perfected. The method further includes causing a transmission of an audit request to the user device relating to the deposit request upon determining the deposit transaction confidence level is below a confidence level threshold. The audit request includes a request to confirm one or more details relating to the deposit request. The method still further includes determining a deposit determination based on a response to the audit response. The deposit determination indicates whether the intended deposit will be executed.