No matching RPIC found for the client

[MeshMIchael]

Hello, 

I have MLE configured and working (checked on other endpoint)

Trying to call 

https://sandbox.api.visa.com/vbs/dapi/v1/transaction_enhanced

request options are: 

const options: any = {
    hostname: 'sandbox.api.visa.com',
    port: 443,
    uri: `https://sandbox.api.visa.com/vbs/dapi/v1/transaction_enhanced?${queryParams}`,
    method: 'POST',
    headers: {
        clientId: 1111,
        'Content-Type': 'application/json',
        Accept: 'application/json',
        'x-pay-token': xPayToken,
        'x-correlation-id': 'XXXX-111111-222222-333333',
        keyId: keyId
    },
    body: postBody,
    json: true
};

Request body is: 

{
        issuerId: '9999',
        companyId: '11112222',
        pagination: {
            pageSize: 10,
            pageNum: '1'
        },
        processorId: '1',
        regionId: '1',
        filters: {
            enhancedData: {
                filterValues: [],
                filterType: 'ENHN_CAT'
            },
            transactionDateTime: {}
        },
        type: 'TRAN_ENHN'
    }

And getting error:

{
    "errorId": "DAPI-GATEWAY-1739725216386",
    "applicationResponseCode": "DAPI-GATEWAY-008",
    "messageDetails": [
        "No matching RPIC found for the client."
    ],
    "timestamp": "2025-02-16 17:00:16.386",
    "httpStatusCode": 404,
    "correlationId": "1739725216_303_810146934_-579f8d9b4-8_VDP_WS"
}

 
Can you please guide me on what body should be sent so I will get the correct results?

[SyedSa]

Hi @MeshMIchael, Thank you for reaching out. An agent will get back to you as soon as possible. Until then, if any community member knows a solution, feel free to reply in this thread.

[DianaVisaPM]

Hey @MeshMIchael,

It looks like you are encountering an issue with the `transaction_enhanced` endpoint. The error message "No matching RPIC found for the client" suggests that there is a problem with the `issuerId`, `companyId`, `processorId`, or `regionId` that you are using in your request body. To resolve this, please ensure that these IDs are correctly configured and registered with Visa.

Here’s a step-by-step guide to help you troubleshoot and correctly configure your request:

1. Verify Credentials and IDs:
- Ensure that the `issuerId`, `companyId`, `processorId`, and `regionId` are correctly configured and valid. These IDs should be obtained from Visa and properly registered.

2. Request Body:
- Double-check the structure of your request body. Here is an example of a properly formatted request body for the `transaction_enhanced` endpoint:

```json
// START 
{
"issuerId": "9999",
"companyId": "11112222",
"pagination": {
"pageSize": 10,
"pageNum": "1"
},
"processorId": "1",
"regionId": "1",
"filters": {
"enhancedData": {
"filterValues": [],
"filterType": "ENHN_CAT"
},
"transactionDateTime": {}
},
"type": "TRAN_ENHN"
}
// END
```

3. Check Request Options:
- Ensure that your request options are correctly configured. Here is an example of how to set up the options in your code:

```javascript
// START 
const options = {
hostname: 'sandbox.api.visa.com',
port: 443,
uri: `https://sandbox.api.visa.com/vbs/dapi/v1/transaction_enhanced?${queryParams}`,
method: 'POST',
headers: {
clientId: 'YourClientId',
'Content-Type': 'application/json',
Accept: 'application/json',
'x-pay-token': xPayToken,
'x-correlation-id': 'XXXX-111111-222222-333333',
keyId: 'YourKeyId'
},
body: JSON.stringify(postBody),
json: true
};
// END 
```

4. Verify x-pay-token:
- Ensure that the `x-pay-token` is correctly generated. This token is crucial for the authentication of your request. You can find more details on how to generate this token in the Visa Developer documentation.

5. Testing and Debugging:
- Use the Visa Developer sandbox environment to thoroughly test your request. Check for any discrepancies in the values being sent.
- Make sure that the IDs and keys you are using are correctly set up in the Visa Developer Portal.

[DianaVisaPM]

Hey @MeshMIchael,

The error message "No matching RPIC found for the client" indicates that the `issuerId`, `companyId`, `processorId`, or `regionId` provided in the request body is not correctly configured or not recognized by the Visa system. Here are some steps to help you troubleshoot and correctly configure your request:

1. Verify Credentials and IDs:
- Make sure that the `issuerId`, `companyId`, `processorId`, and `regionId` are correctly configured and valid. These IDs should be obtained from Visa and properly registered.

2. Check Request Body:
- Double-check the structure and values of your request body. Here is an example of a properly formatted request body for the `transaction_enhanced` endpoint:

```json
// START 
{
"issuerId": "9999",
"companyId": "11112222",
"pagination": {
"pageSize": 10,
"pageNum": "1"
},
"processorId": "1",
"regionId": "1",
"filters": {
"enhancedData": {
"filterValues": [],
"filterType": "ENHN_CAT"
},
"transactionDateTime": {}
},
"type": "TRAN_ENHN"
}
// END 
```

3. Check Request Options:
- Ensure that your request options are correctly configured. Here is an example of how to set up the options in your code:

```javascript
// START 
const options = {
hostname: 'sandbox.api.visa.com',
port: 443,
uri: `https://sandbox.api.visa.com/vbs/dapi/v1/transaction_enhanced?${queryParams}`,
method: 'POST',
headers: {
clientId: 'YourClientId',
'Content-Type': 'application/json',
Accept: 'application/json',
'x-pay-token': xPayToken,
'x-correlation-id': 'XXXX-111111-222222-333333',
keyId: 'YourKeyId'
},
body: JSON.stringify(postBody),
json: true
};
// END 
```

4. Verify x-pay-token:
- Ensure that the `x-pay-token` is correctly generated. This token is crucial for the authentication of your request. You can find more details on how to generate this token in the Visa Developer documentation.

5. Testing and Debugging:
- Use the Visa Developer sandbox environment to thoroughly test your request. Check for any discrepancies in the values being sent.
- Make sure that the IDs and keys you are using are correctly set up in the Visa Developer Portal.