Community
3ds/authenticate enrolled and actionCode fields
The 3ds/authenticate call documentation shows an enrolled field if you click on the response documentation in the middle column of the page, under the request field descriptions. The response JSON that is shown on the right side of the page when you click on the 200 response does not include the enrolled field, and neither does the response in the Sandbox Environment. Should that field be removed from the documentation?
Source for sdkVersion in 3ds/init
The documentation for the sdkVersion field in the 3ds/init call does not state where the value should come from. Is there a call within the SDK that we should make to get this value or do we need to construct it based on the version number from the SDK file name? If we need to construct it, what is the pattern for constructing the name?
Android and iOS app permissions for 3-D Secure Mobile SDK
I've checked the TabaPay documentation and the documentation for the SDK components but cannot find a list of permissions that are required by the 3-D Secure SDK for mobile apps. The SDK documentation mentions getting location information for Android, and the EMV documentation mentions getting Bluetooth information for Android. Are there specific app permissions that are required in order to integrate the 3-D Secure mobile app SDK?
Transaction Retrieve > Fetch accurate Processing Fees
Hello! 👋
Is enhancedResponse needed for production?
The [3D Secure Lookup API call](https://developers.tabapay.com/reference/3dslookup lists the enhancedResponse query parameter as required, and says that in the Sandbox Environment it provides more details. The query parameter is required in the Sandbox Environment. Is it acceptable to use the parameter for the Production Environment, or is it only intended for the Sandbox?
Sandbox AVS test cards
Are there any sandbox cards to test AVS card query to test error validation for cvv and expiry date errors? Also do we always get AVS networkRC 85 in sandbox? How to get 00 for networkRC?
push to card
does push to card required Address Verification services (AVS) ?
Query Card with AVS expiry date validation
Query Card with AVS validates CVV properly but it doesn't validates expiry date. I tried query card with correct account number, cvv and wrong expiry date but it didn't give any error. I thought we were suppose to get error regarding invalid expiry in networkRC but it has 00 value in all cases. Does Query card with AVS validates expiry date? If yes, where is it represented?
is the address and zip code are required for a push transaction ?
is the address & zip code fields are required for a push to debit transaction ?
Query card Push/Pull reponse
Does the push and pull enabled response from query card api actually represent if the customer is eligibile for push and pull transactions? Will there be a scenario when pull enabled is true but the pull transaction being failed? If yes, what scenario?