Community
3-D Secure iOS SDK returns different value from Android SDK
When using test card 5555-5555-5555-4444 to test the 3-D Secure expected error condition, we get a different result from the 3-D Secure mobile app Android SDK than we do from the iOS SDK. That card is supposed to cause a Step Up Authentication is Unavailable condition. When we use the Android SDK we get a NoAction value from the onValidated call in the validateResponse.getActionCode. For the same scenario in iOS the stepUpDidValidate has a null value for validateResponse, and no actionCode value is available. We expect the iOS stepUpDidValidate call to include a valid validateResponse with an actionCode of NoAction.
The Transaction Final Status
When create a transaction by creditcard etc, the Http Status 200 still includes a status field, the values could be https://developers.tabapay.com/reference/resource-status and from the transaction status page, https://developers.tabapay.com/reference/transaction-resource-status it could has some middle status.
Status: Unable to Complete Authentication
The 3ds/lookup and 3ds/authenticate API calls both return a Status. One of the possible status values is U , Unable to Complete Authentication. Should this be interpreted as a "system not available" response, or should it be interpreted as a "failed authentication" response?
JSON Content-types for responses
Hello 👋
API ratelimit?
In our system, we have a scheduled task to send a collection of payments at the same time, but the scheduled task was failed due to connection lost in the middle way.
Transction type when switch to ACH API
we are trying to use the newest ACH API to send payment, but in the original ACH input file, there is no pull/push type, just credit/debit, what is the tx type in the ACH API.
Create Card allows 1 char for first/last name, but 3ds/lookup requires 2 chars
The [Query Card](https://developers.tabapay.com/reference/cardquery), [Create Account](https://developers.tabapay.com/reference/accountcreate), and [Create Transaction](https://developers.tabapay.com/reference/transactioncreate) API calls all allow a single character for the first name and last name fields for the owner, but the [3D Secure Lookup](https://developers.tabapay.com/reference/3dslookup) call requires 2 characters in both. The 2-character requirement is not documented and is inconsistent. I realize that the back-end API that you're using requires a minimum of 2 characters for first and last names, but this should be called out in the documentation, especially because it is inconsistent.
US territories not allowed for 3ds/lookup
The [US state codes](https://developers.tabapay.com/reference/us-state-codes) that are supported by the [Create Account API](https://developers.tabapay.com/reference/accountcreate) include US territories. However, the [3ds/lookup API](https://developers.tabapay.com/reference/3dslookup) call rejects requests for card accounts that are registered with territories. Is this intentional?
Source of version in PullOptions/3DSecure object for Create Transaction
There is a single-digit version string in the PullOption 3DSecure object for [Create Transaction](https://developers.tabapay.com/reference/transactioncreate). Where is the value for that supposed to come from?
XID in Create Transaction
When using 3-D Secure we need to include an XID in the pullOptions 3DSecure object. The documentation for the 3ds/lookup and for 3ds/authenticate say that an XID is returned, but neither JSON sample shows that, and the calls in the Sandbox Environment don't appear to be returning an XID. Are we supposed to be getting this value from somewhere else, such as the processorTransactionID?