Community
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.
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.
Subclient APIs Available?
Hello,
Push to Pre-paid debit cards?
Hello 👋
Links are missing in the docments
In the bottom of this page, https://developers.tabapay.com/docs/how-unified-api-works
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?
Does the tabapay API have a capability to retrieve when a debit card was created?
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.
Generate ACH Input File for FBO2 at the same time
we have a requirement of generating ACH Input file for general tx and and tx that used FBO2, because FBO2 used a different ISO code, so we should generate two files.
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?
SubClient Creation > Settlement, Fees, & Reserve Account optional or required?
Hello,