Overview

Introduction

This guide offers a comprehensive overview of Qolo's Interact (Intra-Request Authorization and Control Transaction) System, which allows Qolo's customers to actively engage in transaction authorization and decision-making. The goal is to detail the authorization flow, testing procedures, response handling, and API integration necessary for successful implementation.

---

Interact Authorization

Interact Authorization is a transaction-processing solution that enables Qolo partners to actively approve, partially approve, or decline transactions in real time.

When a transaction request is initiated, Qolo's Interact system immediately sends an authorization message to the client's system, providing key transaction details. The client then evaluates the request against their internal rules and sends a response—either approving, partially approving, or declining the transaction.

Key Features

• Real-time authorization control – Clients can approve or decline transactions instantly.
• Decision-based processing – Businesses can apply custom rules for authorizing transactions.
• Multiple components for flexibility – Clients can choose how involved they want to be in the transaction decision-making process, based on their operational needs.

Qolo's customers can take full control over transaction approvals, enforce security measures, and enhance financial decision-making using the Interact System.

---

Synchronous vs. Asynchronous

Interact consists of Synchronous and Asynchronous messages, each playing a unique role in the transaction processing lifecycle. Synchronous messages facilitate real-time transaction approvals, allowing clients to make immediate authorization decisions. In contrast, Asynchronous messages handle post-processing transaction updates, providing critical notifications for settlements, reversals, and refunds. This combination ensures efficient and seamless transaction management, with both immediate and follow-up updates catered for.

Synchronous Message

Authorization requests, where the client must decide whether to approve, decline, or partially approve a transaction.

1. A cardholder attempts a purchase at a merchant.
2. Qolo receives the authorization request from the card network.
3. Qolo sends the request to the client’s authorization endpoint for decisioning.
4. The client has up to 3 seconds to respond with:
   • Approve – The transaction is authorized.
   • Partial Approve – A lower amount is approved (if supported by the merchant).
   • Decline – The transaction is rejected.
5. Qolo forwards the final decision to the card network, which informs the merchant.

Asynchronous Message

Non-real-time transaction messages that provide informational updates about transactions after processing. Used for settlements, reversals, refunds, chargebacks, and transaction reconciliation.

1. A merchant settles a batch of transactions at the end of the business day.
2. Qolo receives the settlement data and finalizes the fund movement.
3. Qolo sends a settlement message to the client’s message endpoint with details of the transaction.
4. The client logs the settlement information and updates their internal transaction records.

---

Related Topics

• Interact Components
• Interact Testing
• Interact Best Practices and Troubleshooting