Authorizations
Bearer authentication header of the form Bearer <secret_key>, where <secret_key> is your secret_key.
Body
Payment object associated with the current session.
Session language, used to launch HPP with desired language.
ar, en "en"
Please contact your integration manager to get the merchant code.
"code provided to you from Tabby side"
Used for redirecting the customer after Tabby Checkout flow. Required for Web integration, optional for Mobile App integration.
If you already have token, you can pass it there. Authorization header still requires Secret Key.
Response
Success. Checkout session object is returned.
Unique identifier for the checkout Session, assigned by Tabby.
"session id, uuid format"
Some details associated with the current session.
In the response, this field will be filled with token value if session status is 'approved'.
You can use that token for Tokenized Payments and Web Checkout.
null
Payment object associated with the current session.
Status of the current session. Used at the pre-scoring and session creation steps.
createdis returned when the request is approved and the customer is eligible to use Tabbyrejectedmeans that there are no available products for a customerexpiredandapproved- used for specific type of integration, kindly ignore them if not communicated directly
created, rejected, expired, approved "created"