Card Transactions Verification

This document describes the workflow for verifying card transactions via webhook integration. It outlines how partners can receive transaction verification messages and interact with clients to complete the verification process.

Workflow Overview

Step 1: Verification Trigger

• When a transaction requires verification (such as 3DS or OTP), VISA triggers the process.

• MuseCard receives the verification event from VISA.

Step 2: Webhook Notification to Partner System

MuseCard sends a webhook notification to the Partner System:

• CARD_TX_OOB: Out-of-band verification (client confirmation required).

• CARD_TX_OTP: One-time password (OTP) verification.

• CARD_TX_3DS_URL: 3D Secure verification URL.

Step 3: Client Interaction

The Partner System forwards the verification message to the client:

• For CARD_TX_OTP, the client inputs the OTP code.

• For CARD_TX_3DS_URL, the client clicks the verification URL to complete the 3D Secure process.

• For CARD_TX_OOB, the Partner System pushes a message to the client for manual confirmation.

2. CARD_TX_OOB Model (Out-of-Band Verification)

1. The client receives the verification request via the Partner System.

2. The client confirms or declines the transaction.

3. The Partner System sends the result to MuseCard via API:

   • POST /txn-verification-confirm — to confirm the transaction.

   • POST /txn-verification-decline — to decline the transaction.

4. MuseCard processes the response and sends the result to VISA via callback.

---

3. Key Notes

• All webhook events are sent to the Partner System in real time.

• The Partner System is responsible for delivering the message to the client.

• Timely processing of verification responses is crucial to avoid transaction delays.