ANSWERED

soft descriptor in the create transaction API

Do we need to send the Full address inside the softdescriptor object. Some of the required fields are ambiguous.

ANSWERED

Is it possible to get details about these internal error codes?

"EC": "3C55602E",

ANSWERED

ACH Input CSV file format

we are switch to use Kotlinx Dataframe lib to generate the standard csv format for the ACH Input file, to replace our former manual text producing.

ANSWERED

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.

ANSWERED
ANSWERED
ANSWERED

JSON Content-types for responses

Hello 👋

ANSWERED

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.

ANSWERED

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.

ANSWERED

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.


Questions? Contact Sales or make a post