How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

TabaPay 3D Secure API

The 3D Secure API from TabaPay — 3 operation(s) for 3d secure.

TabaPay 3D Secure API is one of 16 APIs that TabaPay publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include 3D Secure. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 3 paths, and defines 39 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://{FQDN}:{PORT}.

3 operations 3 paths 39 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.tabapay.com
Authentication
HTTP Bearer, API Key
License
All rights reserved
Resource Areas
1

Authentication & Security 2

TabaPay 3D Secure API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). An API key is passed in the header as Authorization (custom-header). By default, every request must be authenticated.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 POST. Each is listed below with its method, path, parameters, and response codes.

3D Secure 3
POST
/v2/clients/{ClientID}/3ds/authenticate
3D Secure Authenticate
3dsauthenticate 1 param body → 200
POST
/v2/clients/{ClientID}/3ds/init
3D Secure Initialize
3dsinit 1 param body → 200207404
POST
/v2/clients/{ClientID}/3ds/lookup
3D Secure Lookup
3dslookup 2 params body → 200207404

Schemas 39

The contract defines 39 schemas that model the data the API accepts and returns. The most detailed are 3dsLookupResponse (17 properties), 3dsAuthenticateResponse (12 properties), browser (11 properties), 3dslookup (9 properties). Each schema is shown below with its type and property counts.

productCode
string
3-character [Product Code](lookupproduct-code)
3dsID
string
3dsID returned from [3dsinit](https://developers.tabapay.com/reference/3dsinit/)
screenHeight
string
Deprecated Screen Height
authenticationIndicator
string
2-digit [Authentication Indicator](https://developers.tabapay.com/reference/lookup/authentication-indicator)
SC
integer
[HTTP Status Code](https://developers.tabapay.com/reference/http-status-codes/)
transactionType
string
C is the only [Transaction Type](https://developers.tabapay.com/reference/lookup/transaction-type) supported.
EC
string
Internal Error Code. This is used to help TabaPay team members trace an error.
colorDepth
string
Deprecated Color Depth
EM
string
Short description of the error if an error occurred.
line2
string
Address Line 2 Optional
3dsauthenticate
object
2 properties 2 required
screenWidth
string
Deprecated Screen Width
deviceChannel
string
Either Browser or SDK
userAgent
string
Deprecated User Agent
3dsAuthenticateResponse
object
12 properties
3dslookup
object
9 properties 7 required
state
string
State Code [State Code](https://developers.tabapay.com/reference/us-state-codes/) must be a valid 2-character code if country is [840](https://developers.tabap…
country
string
[Country Code](https://developers.tabapay.com/reference/country-codes/) Optional. Default is 840
3dsLookupResponse
object
17 properties
3dsVersion
string
The 3D Secure Version that was used to process this request. Expected values are of the form: 2.X.X
city
string
City
apiResponseSCECEM
object
3 properties
language
string
Deprecated Language
sdkSessionID
string
Mobile flow referenceID (used in conjunction with init.sdkVersion, comes from the SDK's setup.onComplete) Required if the device channel is SDK.
browser
object
Browser Information. For more information on these fields see [here](https://developers.tabapay.com/reference/browser-fields)
11 properties 1 required
zipcode
string
Zip Code If country is 840, zipcode must be 5 or 9 digits. If country is 124, zipcode must be in the A1A 1A1 format. Zip codes from other countries will not be…
3dsInitResponse
object
6 properties
amount
string
See how to [properly format an amount](/reference/datahow-to-specify-an-amount-value).
browserInfo
string
Concatenated [Browser Data Fields](https://developers.tabapay.com/reference/browser-fields). Concatenate the below fields (in order!) with the | 1. javascriptE…
line1
string
Address Line 1
transactionMode
string
1-character [Transaction Mode](https://developers.tabapay.com/reference/lookup/transaction-mode)
phone
object
Phone object
2 properties 1 required
javascriptEnabled
boolean
Deprecated Javascript Enabled
ipAddress
string
Deprecated IP Addresses in IPv4 or IPv6 formats are accepted.
3dsinit
object
3 properties 1 required
apiResponseSCEC
object
2 properties
currency
string
[ISO 4217](https://en.wikipedia.org/wiki/ISO4217) 3-Digit [Currency Code](https://developers.tabapay.com/reference/currency-numbers/). Optional. Default is 840
javaEnabled
boolean
Deprecated Java Enabled
header
string
Deprecated Header

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tabapay-3d-secure-api-openapi.yml Raw ↑

Other APIs TabaPay publishes across the network.

TabaPay Account API
TabaPay Bank API
TabaPay Card API
TabaPay Client API
TabaPay FXRate API
TabaPay Health API
TabaPay Key API
TabaPay Ledger API
TabaPay OFAC API
TabaPay SubClient API
TabaPay Tag API
TabaPay Transaction API
Where this information came from

This is an independent, third-party profile of TabaPay 3D Secure API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.