Visa BIN Attribute Sharing Service missing fields

[AbhishekS]

Hi,

Testing the Visa BIN Attribute Sharing Service (VBASS) - Full Bin List, noticed that out of the ~3400 bins provided, ~650 are missing the country code i.e the "accountCtryAlpha2Code" field is a blank string. Same with a few which are missing the "accountBusName" field.

I understand that the fields are marked optional in the API Reference but the other fields also marked so are consistent, e.g currency etc.

So my query was if this discrepancy/data is isolated to the sandbox API or will similar issues arise in a production environment?

Thanks in advance.

Regards

Abhishek

[SLi]

Hi @AbhishekS,

The sandbox environment is designed to provide a general view and guide of the endpoint request and response structure. The data in the sandbox is limited and may only cover a small subset of possible fields. Since sandbox is a static test environment, you may not be able to test all API functionality or see the full list of optional fields in the response. The idea is that you can begin development and self-testing in sandbox. Once satisfied with how your solution is looking and working, then promote to production environment for live testing.

Can you please share the API endpoint URL and test payload so I can check with our product team to confirm? Thanks.

[AbhishekS]

Hi,

Thanks for replying.

The endpoint in use is 'https://sandbox.api.visa.com/v1/binRangeDetails'.

Not sure how the payload will help but it looks like '{"requestHeader": {"requestTS": "2021-05-24T05:21:07.000", "requestMessageID": "test999" }, "requestData": {"binRangeSearchIndex":"0", "binRangeCount": "500"}}' with incremental search index until the response flag turns negative.

Thanks & Regards

[SLi]

Hi @AbhishekS,

If a field is marked optional in the API reference, we populate that field when the value is available. In most cases we have the values for all the fields and they are populated and in some cases they are not populated. If a field is marked required in the API reference, it will always have a value populated. In sandbox we have dummy data but it follows the API documentation guidelines. Hope this helps, please let us know of any other questions.

[AbhishekS]

Hi,

I understand the sandbox dummy data follows the API guidelines properly and we have a mechanism for inferring data points relevant at our end.

The question I had referred to the data availability since 650 out of ~3400 is well beyond our fault tolerance limits, should we expect similar fractions in the actual data as well or was this specific to sandbox/dummy data.

Thanks & Regards,

Abhishek

[SLi · Accepted solution]

Hi @AbhishekS,

We have close to 100% availability(almost all records have the country/region columns populated) at this point in the prod data. But that can change as this data is not static, though we expect these columns to have a value most of the times.

[vakilpaul2]

Thanks for the clarification.