Community

We have an unique situation 1. We created a transaction of 100 USD with a reference ID 2. Then after settlement, we created the 2 partial refunds (delete transaction with reversal) of 50 each How do we distinguish between these two partial refunds in the settlement file?

Hello, Can someone clarify what does the country means here, is this where the card is issued or is this is the place where the card holder lives? ```Text Json { "SC": 200, "EC": "0", "card": { "bin": "411111", "last4": "1111", "nameFI": "Financial Institution Name", "pull": { "enabled": true, "network": "Visa", "regulated": true, "currency": "840", "country": "840" }, "push": { "enabled": true, "network": "Visa", "type": "Debit", "regulated": true, "currency": "840", "country": "840", "availability": "Immediate" } } } ```

When we are creating a transaction after the successful 3ds verification, do we need to pass the ECI and UCAF values? Does passing or not passing will make the difference in liability shift? thanks

Do we need to send the Full address inside the softdescriptor object. Some of the required fields are ambiguous. Can you please clarify? thanks

"EC": "3C55602E", "EC": "39551365", "EC": "3C5E5662", More details is better, would be nice for us to understand what really happened with the transaction

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. Last time I remembered there is an email from Tabapay that point out our **commas** in the value will cause the tabapay processing failed. Now when we switched to use DataFrame, it will use the standard csv format to handling the value with commas and wrap them into a pair of `""`, is this working in Tabapay side. For example: Given csv cell value `My Comp, Ltd` , we treated them in former csv handling like this `My Comp Ltd`. Now switching to use Dataframe, it becomes: `"My Comp, Ltd"` , is this working in the Tabapay server?

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`. iOS Version: 2.2.5-6 Android Version: 2.2.7-3

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. I wonder, when creating tx direct, such as pull from credicard, or push to debit card, what is the final status of this Create Transaction API will be ?

Hello :wave: Per our discussion \[here](<https://developers.tabapay.com/discuss/62a41c9cc84c6100304af3f0>) we discussed TabaPay updating all API endpoints' content-type headers to JSON. I was wondering if there's an update to that. We're refactoring our network module and finding it difficult to override our responses from TabaPay accordingly. Thanks!