Request Parameters

The POST request via Web SDK must contain the following mandatory components:

• Payment Data
• Customer Data

Payment Data

📘

Important

To avoid CORS errors, ensure that the Web SDK widget is hosted on the same page as the shop_url, and the shop_url value passed during the Web SDK initialization.

Customer Data

📘

Info

*These fields are recommended to be sent as they may be needed in case of chargeback disputes.

Response Parameters

Web SDK Responses

Initial Response Parameters

• Initial Response is a Payabl. response to get a Web SDK session_id
• Received as a response after a request Get a Unique Web SDK session_id has been sent.

Data Fields:

Here, the transactionid is a unique payabl. identifier assigned to each transaction processed through the Web SDK. It is used to track and reference specific transactions within the payabl. system.

In the initial response parameters, the transactionid is not mandatory as it si generated only after a successful payment transaction. The initial response primarily includes parameters necessary to set up the payment session, such as session_id, which is used to initialize the SDK payment form.

• When We Gettransactionid : you receive transactionid in the response after the payment process is completed successfully. The transactionid is included in the callback response to indicate that the transaction has been processed and recorded.
• When We Don't Gettransactionid : during initial setup and session creation phase, you do not receive a transactionid. At this stage, the focus is on generating a session_id to initialize the payment form. The transactionid is only provided after the actual payment transaction is attempted and processed.

Response Callback Notifications

• Callback Notifications provide updates on transactions' outcome using a Notification URL. Notification URL can be provided in each request separately or can be set as a default value for your account.
• payabl. sends Callback Notifications with statuses to Notification URL immediately after receiving a status from payment system.

Example:

{
   "status":"APPROVED",
   "metadata":{
      "errorcode":"0",
      "type":"capture",
      "errormessage":"",
      "orderid":"payabl-Test",
      "transactionid":"213548331"
   }
}

Statuses:

Metadata:

Final Response Parameters

• Final Response Parameters are the detailed information returned by the Payabl. API after a payment transaction
• Received upon completion of the payment transaction

Data Fields:

For the further inquiries, please contact our Technical Support Team Email: [email protected] (available Monday to Friday from 09:00 to 17:00 CET/CEST)