Community
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?
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?