Inquiry API - May I please get example use cases for InquiryRequest, IssuerReject-3 and EchoMess

[MAC]

Please may I request a qualified answer on when I would be using these 3 Request types please?

InquiryRequest, IssuerReject-3 & EchoMessage

[SyedSa]

Hi @MAC, Thank you for reaching out. An agent will get back to you as soon as possible. Until then, if any community member has information that may be helpful, feel free to reply in this thread.

[DianaVisaPM · Accepted solution]

Hi @MAC,

Visa Developer Portal API Use Cases

1. InquiryRequest
Use Case: The `InquiryRequest` is used to fetch detailed information regarding a particular transaction or account. This can be used in scenarios where a financial institution or merchant needs to verify transaction details, check account balances, or confirm the status of a payment.

Example Scenarios:
- Account Verification: A bank wants to verify the balance or transaction history of a customer's account.
- Transaction Details: A merchant needs to retrieve detailed information about a specific transaction to resolve a dispute or verify payment.
- Fraud Prevention: A financial institution wants to verify suspicious transactions to prevent fraud.

2. IssuerReject-3
Use Case: The `IssuerReject-3` request type is used when the issuing bank declines a transaction. This can be due to various reasons such as insufficient funds, account restrictions, or suspected fraud.

Example Scenarios:
- Insufficient Funds: A transaction is declined because the account does not have enough funds to cover the purchase.
- Account Restrictions: The account has restrictions that prevent the transaction from being approved.
- Suspected Fraud: The transaction is flagged as potentially fraudulent, and the issuer decides to reject it to protect the account holder.

3. EchoMessage
Use Case: The `EchoMessage` request type is used primarily for testing purposes to verify the connectivity and response time between systems. It ensures that the communication channel between the client and the Visa network is functioning correctly.

Example Scenarios:
- System Testing: Before going live, a developer uses `EchoMessage` to test the connection and ensure that the integration with the Visa API is working as expected.
- Health Check: Periodic checks to confirm that the connection to the Visa network is stable and can respond to requests within acceptable timeframes.
- Performance Monitoring: Continuous monitoring of the response times to ensure the system is performing efficiently.

Summary Table

Request Type	Use Case Description	Example Scenarios
InquiryRequest	Fetch detailed information regarding a transaction or account.	Account verification, transaction details retrieval, fraud prevention.
IssuerReject-3	Used when the issuing bank declines a transaction.	Insufficient funds, account restrictions, suspected fraud.
EchoMessage	Used for testing connectivity and response time between systems.	System testing, health check, performance monitoring.

These use cases and examples can help you determine when to use each request type in your integration with the Visa Developer Portal APIs.

[MAC]

May I please confirm the direction and use of these message flows - from an Issuer perspective please?

As an Issuer on 'Lite' or 'Full',  do they come into us and we provide the responses?

[DianaVisaPM]

Hey @MAC,

Sure, I can help explain the use cases and message flows for InquiryRequest, IssuerReject-3, and EchoMess from an Issuer perspective. These message flows are part of the Visa Token Service (VTS) and help issuers manage various aspects of token lifecycle management and ensure system integrity.

1. InquiryRequest
Use Case:
- InquiryRequest is typically used to request information about a token or to inquire about the status of a token. This can include details such as the token's current status (e.g., active, suspended, or deactivated), the associated cardholder information, or the device information.

Direction and Use:
- From an Issuer perspective, InquiryRequest messages are sent to the issuer from Visa or a token requestor to fetch the required information.
- Issuer Response: As an issuer, you are expected to process these inquiries and respond with the requested information regarding the token.

Example:
```json
{
"requestType": "InquiryRequest",
"tokenReferenceId": "1234567890",
"inquiryType": "TokenStatus"
}
```

2. IssuerReject-3
Use Case:
- IssuerReject-3 is used when an issuer needs to reject a token lifecycle management request. This could be due to various reasons such as validation failures, risk assessments, or policy violations.

Direction and Use:
- From an Issuer perspective, IssuerReject-3 messages are sent by the issuer to Visa or a token requestor to indicate that the request has been rejected.
- Issuer Action: As an issuer, upon receiving a token lifecycle request (e.g., provisioning, deactivation), you evaluate the request and send an IssuerReject-3 message if the request is to be denied.

Example:
```json
{
"responseType": "IssuerReject-3",
"tokenReferenceId": "1234567890",
"reasonCode": "InvalidCardholder",
"reasonDescription": "The cardholder information provided is invalid."
}
```

3. EchoMess
Use Case:
- EchoMess is used to verify the connectivity and responsiveness of the issuer's systems. It acts as a heartbeat or ping to ensure that the communication channels between Visa and the issuer are functioning correctly.

Direction and Use:
- From an Issuer perspective, EchoMess messages are sent to you from Visa to check the system's health and response time.
- Issuer Response: As an issuer, you should respond to EchoMess messages promptly to confirm that your systems are operational and responsive.

Example:
```json
{
"messageType": "EchoMess",
"timestamp": "2023-10-10T12:00:00Z"
}
```

Response Example:
```json
{
"messageType": "EchoMessResponse",
"timestamp": "2023-10-10T12:00:01Z",
"status": "Success"
}
```

Confirmation for Issuer on 'Lite' or 'Full' Service
- Whether on 'Lite' or 'Full' service, these messages (InquiryRequest, IssuerReject-3, and EchoMess) are directed to you as the issuer. You will receive these messages and are responsible for providing the appropriate responses based on the request and your internal processing logic.