Community

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?

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?

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?

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?

The [3D Secure Lookup API call](https://developers.tabapay.com/reference/3dslookup lists the enhancedResponse query parameter as required, and says that in the Sandbox Environment it provides more details. The query parameter is required in the Sandbox Environment. Is it acceptable to use the parameter for the Production Environment, or is it only intended for the Sandbox?