Community

The [3-D Secure lookup API](https://developers.tabapay.com/reference/3dslookup) requires a `browser` object. We're processing in a mobile app and not within a browser. We're using the Cardinal Mobile SDK to perform the device data collection, but it does not appear to return data that can be used to populate the `browser` object. Is the expectation that we should create a `browser` object with only the `deviceChannel` field (set to `SDK`)? If the `deviceChannel` is set to `SDK` does the `3ds/lookup` return an error if the mobile device data collection step is not peformed?

We're using the Cardinal Mobile SDK for our mobile app for 3-D Secure processing. The steps from the [sequence diagram in the documentation](https://developers.tabapay.com/reference/how-to-use-the-3ds-sdk-starter-guide#example-flow) are: 1. Call `3ds/init`. It returns a `3dsID` and JWT within the response. 2. Create a session with the Cardinal Mobile SDK using the JWT from the `3ds/init` response, [which returns a `consumerSessionId`](https://developers.tabapay.com/reference/how-to-use-the-3ds-sdk-starter-guide#10-use-the-sdk-to-authenticate-the-jwt-and-begin-collecting-device-data). The [documentation for `3ds/lookup`](https://developers.tabapay.com/reference/3dslookup) says to use the `3dsID` from the `3ds/init` response. Is the `consumerSessionId` the same value as the `3dsID` from `3ds/init`? If so, are we expected to ensure that the values are the same? If they are not intended to be the same, what is the `consumerSessionId` value used for?

Hello 👋 We're seeing this pull error in sandbox, however not sure why: POST https://api.sandbox.tabapay.net:10443/v1/clients/SAAINT.../transactions ``` { "referenceID": "X8gEG9hzeRNO1Ot", "type": "push", "accounts": { "sourceAccountID": "AAgoNTEEAUbkxhzYQTDWlw", "destinationAccountID": "SJQqxYgUIUxQfhv6pbaBsQ" }, "amount": "12.00", "currency": "840" } ``` Response: ``` { "SC": 207, "EC": "3C5E9E00", "transactionID": "gJQ65MwVKWtQYNOodwfzig", "network": "Visa", "status": "UNKNOWN", "errors": [ "000E7740", "24584853" ] } ```

From the description of ACH Return file, https://developers.tabapay.com/docs/overview-of-ach#ach-returns There are 3 **Amount** in the Return file format table, I can not build a sample for my tests. Please provide a Sample.

Hi, We are seeing a lot of declines for payments on cards that have been used before. For example, two different Mastercards were declined with a NC of 82. On another Visa card, we received a NC 59. An hour later, the card was used and the payment was accepted. Any reason why this is occuring?

Good day, Since early to mid February we have been receiving some null fields in the AVS response when querying cards with the AVS flag turned on. Previously: GetCard Result: {"Data":{"card":{"Pull":{"Enabled":true,"Network":"Visa","Type":"Debit","Regulated":true,"Currency":"840","Country":"840","Availability":null},"Push":{"Enabled":true,"Network":"Visa","Type":"Debit","Regulated":true,"Currency":"840","Country":"840","Availability":"Immediate"}},"AVS":{"NetworkRC":"85","AuthorizeID":"163948","ResultText":"NOT DECLINED","CodeAVS":"Y","CodeSecurityCode":"M","EC":null},"Fees":null} Now: GetCard Result: {"Data":{"card":{"Pull":{"Enabled":true,"Network":"Visa","Type":"Credit","Regulated":true,"Currency":"840","Country":"840","Availability":null},"Push":{"Enabled":true,"Network":"Visa","Type":"Credit","Regulated":true,"Currency":"840","Country":"840","Availability":"Next Business Day"}},"AVS":{"NetworkRC":null,"AuthorizeID":null,"ResultText":"NOT DECLINED","CodeAVS":null,"CodeSecurityCode":"M","EC":null},"Fees":null} We haven't made any code change to this implementation in a while and this is causing an issue on our website when doing pre-transfer and pre-account creation checks. Was this change deliberate on the Tabapay system or is it an intermittent issue with the AVS fields sometimes returning null that we should plan for?

After adding the optional Soft Descriptor in the pull transaction request body, and create transaction by Apple Pay, it failed with a 403 EC. EC:403, EM: "Soft Description" Soft Description can only be applied on card pay?

After adding the optional Soft Descriptor in the pull transaction request body, and create transaction by Apple Pay, it failed with a 403 EC. EC:403, EM: "Soft Description" Soft Description can only be applied on card pay?

Basically, we want to see how old a Debit Card is.. is it possible to see that in any of the APIs? We currently use your api's to do AVS and then accept payments.

Are we supposed to receive a CSV file with the delete transaction(reversal) API ? Are we should use the successful response in the API itself and assume it is settled?