logo
Documentation Powered by ReDoc

JumiaPay API

Welcome to JumiaPay API Documentation!

JumiaPay API will allow you to easily start accepting payments online through a secure one step checkout experience.

With that said, start learning how to integrate our API on your application.

Authentication

Authenticate your API calls by including the apikey header of every request you make. API requests made without authentication will fail with the status code 401: Unauthorized.

Note that API keys both for staging and production will be shared by our team via encrypted email.
For more details about this process check out these 'Get Started' steps.

API Endpoints

When calling our API, include the URL to the API service for the corresponding environment:

Available Payment Options

Get Payment Options

Payment Options API is an API responsible for listing all shops and their respective payment options available for a specific merchant

path Parameters
userType
required
string

user type must be either "regular" or "guest"

header Parameters
apikey
required
string

Fill in with the API key shared by our team

Content-Type
required
string
Example: application/json

The Content-Type (only application/json is supported)

Request Body schema: application/json
merchantIdentifier
required
string

The email of the merchant.

Responses

200

Success response if the merchant is active, if not, data list will be empty

400

Bad Request: The request was unacceptable, due to missing required parameter

401

Unauthorized: Missing or invalid apiKey provided

405

HTTP method not supported

500

Something went wrong while communicating with the server

post/merchant/payment-options/{user-type}

Sandbox URL

https://api-sandbox-pay.jumia.com.ng/merchant/payment-options/{user-type}

Production Url

https://api-pay.jumia.com.ng/merchant/payment-options/{user-type}

Request samples

Content type
application/json
Copy
 Expand all Collapse all
{}

Response samples

Content type
application/json
Copy
 Expand all Collapse all
{
  • "available_options":
    [
    ]
}

Purchases

Create Purchase V2.

The Create Purchase V2 request allows you to process transactions through JumiaPay. For detailed information about how our Purchases feature works, the purchases possible status and how to simulate them, give a look at our Integration Guides.

path Parameters
shopConfigId
required
string <uuid>

Merchant shop configuration id provided by JumiaPay.

header Parameters
apikey
required
string

Fill in with the API key shared by our team

Content-Type
required
string
Example: application/json

The Content-Type (only application/json is supported)

Request Body schema: application/json
description
required
string [ 2 .. 254 ] characters

Brief description of the purchase. This description is for internal use only, it will not be visible to the customer.

amount
required
object

Order amount object

consumer
required
object

Customer's information necessary to create a purchase.

merchant
required
object

Merchant fields object

basket
required
object

Object with product(s) or service(s) data. This data will be shown to the customer in the Cart Detail on JumiaPay website.

expirationTime
integer [ 1 .. 262980 ]

The period of time in minutes provided by the merchant to JumiaPay for the customer to finish his purchase. The customer has 120 minutes if the value is not given by default.

shippingAddress
object

Shipping data to which the products will be delivered.

billingAddress
object

Billing data information.

additionalData
object <= 4096 characters

Additional data with all extra information about the purchase

Responses

201

Created

400

Bad Request: The request was unacceptable, due to missing required parameter

401

Unauthorized: Missing or invalid apiKey provided

403

The merchant does not have access to create new purchases.

404

The resource provided was not found

405

HTTP method not supported

422

The request was well-formed but was unable to be followed due to semantic errors

500

Something went wrong while communicating with JumiaPay

post/v2/merchants/{shopConfigId}/purchases

Sandbox URL

https://api-sandbox-pay.jumia.com.ng/v2/merchants/{shopConfigId}/purchases

Production Url

https://api-pay.jumia.com.ng/v2/merchants/{shopConfigId}/purchases

Request samples

Content type
application/json
Copy
 Expand all Collapse all
{
  • "description": "JumiaPay order",
  • "expirationTime": 30,
  • "amount":
    {
    },
  • "merchant":
    {},
  • "consumer":
    {
    },
  • "basket":
    {
    },
  • "shippingAddress":
    {
    },
  • "billingAddress":
    {
    },
  • "additionalData": "{value1: value 1, value2: value 2}"
}

Response samples

Content type
application/json
Copy
 Expand all Collapse all
{}

Verify Status of Purchase

The Verify Status of Purchase request gives you visibility on the status changes of a purchase until its current status.

header Parameters
apikey
required
string

Fill in with the API key shared by our team

Content-Type
required
string
Example: application/json

The Content-Type (only application/json is supported)

Request Body schema: application/json
shopConfig
required
string (ShopConfig)

Merchant token provided by JumiaPay to identify your shop. This parameter can be found on JumiaPay Business, in the ‘ShopConfigurations’ sub-module with the name Shop Key.

transactionId
required
string

transactionId corresponds to the Purchase Id provided by JumiaPay. This parameter is sent on the success response of Create Purchase request.

transactionType
required
string
Value: "Purchase"

Type of the transaction. The allowed value is "Purchase".

Responses

200

Success

400

Bad Request

401

Unauthorized: Missing Shop Config or API Key

post/merchant/transaction-events

Sandbox URL

https://api-sandbox-pay.jumia.com.ng/merchant/transaction-events

Production Url

https://api-pay.jumia.com.ng/merchant/transaction-events

Request samples

Content type
application/json
Copy
 Expand all Collapse all
{
  • "shopConfig": "YOUR_SHOP_KEY",
  • "transactionId": "AAEAAADpDFehqbrgASaL1jF9DYX6z4t9_bo3Sdb3adFUmCDS_Og3vBc4",
  • "transactionType": "Purchase"
}

Response samples

Content type
application/json
Copy
 Expand all Collapse all
{
  • "success": true,
  • "type": "single",
  • "payload":
    [
    ]
}

Cancel Purchase

The Cancel Purchase request enables you to cancel a purchase when it is in one of the following status:

  • Created: no money has been captured from the customer Payment Instrument yet, which means that the money necessary for the purchase to go forward is still on the customer side.
  • Confirmed or Committed: at this stage, the capture of the money was already done, which means that the money necessary for the purchase to go forward is already on JumiaPay side. Please note that if the purchase is cancelled at this stage, the amount captured from the customer Payment Instrument will not be sent back to his Payment Instrument, but will be released on the customer’s JumiaPay wallet instead.

After a purchase is cancelled, the customer will be able to see it as 'Failed' on his JumiaPay account.

header Parameters
apikey
required
string

Fill in with the API key shared by our team

Content-Type
required
string
Example: application/json

The Content-Type (only application/json is supported)

Request Body schema: application/json
shopConfig
required
string (ShopConfig)

Merchant token provided by JumiaPay to identify your shop. This parameter can be found on JumiaPay Business, in the ‘ShopConfigurations’ sub-module with the name Shop Key.

purchaseId
required
string

Purchase Id provided by JumiaPay. This parameter is sent on the success response of Create Purchase request.

Responses

200

Success

400

Bad Request

401

Unauthorized: Missing Shop Config or API Key

post/merchant/cancel

Sandbox URL

https://api-sandbox-pay.jumia.com.ng/merchant/cancel

Production Url

https://api-pay.jumia.com.ng/merchant/cancel

Request samples

Content type
application/json
Copy
 Expand all Collapse all
{
  • "shopConfig": "YOUR_SHOP_KEY",
  • "purchaseId": "PURCHASE_ID"
}

Response samples

Content type
application/json
Example
Success
Copy
 Expand all Collapse all
{
  • "success": true,
  • "type": "single",
  • "payload": { }
}

Refunds

Create Refund

The Create Refund request allows you to refund purchases made by your business through JumiaPay. A refund can only be made when the purchase is completed.

After a refund is created, the customer will be able to see the record of the refund on his JumiaPay account.

For detailed information about how our Refunds feature works and the refunds possible status, give a look at our Integration Guides.

header Parameters
apikey
required
string

Fill in with the API key shared by our team

Content-Type
required
string
Example: application/json

The Content-Type (only application/json is supported)

Request Body schema: application/json
shopConfig
required
string (ShopConfig)

Merchant token provided by JumiaPay to identify your shop. This parameter can be found on JumiaPay Business, in the ‘ShopConfigurations’ sub-module with the name Shop Key.

refundAmount
required
string

Amount to refund. This amount cannot exceed the purchase amount.

The refundAmount can have up to 2 decimal places. A decimal point must be used to separate the integer part from the fractional part of the number. Example: 10000.99

refundCurrency
required
string
Enum: "NGN" "EGP" "GHS" "KES" "MAD" "XOF" "TND" "UGX"

Refund currency corresponds to official ISO 4217 currency codes:

  • Nigeria: NGN
  • Egypt: EGP
  • Ghana: GHS
  • Kenya: KES
  • Morocco: MAD
  • Ivory Coast: XOF
  • Tunisia: TND
  • Uganda: UGX

refundCurrency must be the same as the priceCurrency of the corresponding purchase.

description
required
string

Brief description of the refund. This description is for internal use only, it will not be visible to the customer.

purchaseId
required
string

Purchase Id provided by JumiaPay. This parameter is sent on the success response of Create Purchase request. You can either send us this parameter or the purchaseReferenceId.

purchaseReferenceId
required
string <= 255 characters

Merchant’s unique reference id generated by you for the purchase (merchantReferenceId). You can either send us this parameter or the purchaseId.

referenceId
required
string <= 255 characters

Merchant’s unique reference id generated by you for the refund. This id is saved on JumiaPay whether the refund completes or fails.

Responses

200

Success

400

Bad Request

401

Unauthorized: Missing Shop Config or API Key

post/merchant/refund

Sandbox URL

https://api-sandbox-pay.jumia.com.ng/merchant/refund

Production Url

https://api-pay.jumia.com.ng/merchant/refund

Request samples

Content type
application/json
Example
Purchase Registered in JumiaPay
Copy
 Expand all Collapse all
{
  • "shopConfig": "YOUR_SHOP_KEY",
  • "refundAmount": 5,
  • "refundCurrency": "NGN",
  • "description": "Refund for order #9182",
  • "purchaseId": "AAEAAADpDFehqbrgASaL1jF9DYX6z4t9_bo3Sdb3adFUmCDS_Og3vBc4",
  • "purchaseReferenceId": "",
  • "referenceId": "YOUR_UNIQUE_REFUND_REFERENCE_ID"
}

Response samples

Content type
application/json
Copy
 Expand all Collapse all
{
  • "success": true,
  • "type": "single",
  • "payload": [ ]
}

One Click and Recurring Payments

This process allows you to create an agreement between a merchant's shop and a customer, which enables the merchant to debit the customer's JumiaPay account, or the underlying payment method, without customer interaction.

If the agreement is successfully created, you will receive an Agreement Callback with an Agreement Token, which can then be used in Create Purchase V2 with Agreement Token.

Do note that One Click and Recurring Payments may not be available for every merchant, and are subject to additional approval.

Create Agreement for One Click

Obtain a redirect URL to initiate creation of an Agreement Token. Please redirect the customer to this URL, and If successful, the Agreement Token will be received via Agreement Callback.

In order to receive the callback, please add these query parameters to the URL provided in the respose when redirecting:

  • returnUrl (Required, with max length of 1023 characters) - URL to redirect the user back to the merchant
  • externalRequestId (Required, with max length of 100 characters) - External request-id provided by the merchant to identify which user belongs to this operation
  • callbackUrl (Required, with max length of 1023 characters) - URL where JumiaPay will send an HTTP callback to the merchant when the agreement's process creation was done

The Agreement Token is linked to a specific shopConfigId , and can not be used or shared with different shops, even at the same merchant.

path Parameters
shopConfigId
required
string <uuid>

Merchant shop configuration id provided by JumiaPay.

header Parameters
apikey
required
string

Fill in with the API key shared by our team

Content-Type
required
string
Example: application/json

The Content-Type (only application/json is supported)

Responses

200

Success

400

Bad Request: The request was unacceptable, due to missing required parameter

401

Unauthorized: Missing or invalid apiKey provided

403

The merchant does not have the feature enabled.

404

The resource provided was not found

405

HTTP method not supported

500

Something went wrong while communicating with the server

get/v2/merchants/{shopConfigId}/recurring-types/one-touch

Sandbox URL

https://api-sandbox-pay.jumia.com.ng/v2/merchants/{shopConfigId}/recurring-types/one-touch

Production Url

https://api-pay.jumia.com.ng/v2/merchants/{shopConfigId}/recurring-types/one-touch

Request samples

Copy
curl -X GET \
  'https://api-staging-pay.jumia.com.ng/merchants/{shopConfigId}/recurring-types/one-touch' \
  -H 'apikey: <YOUR_API_KEY>' \
  -H 'Content-Type: application/json' \
  -H 'cache-control: no-cache' \
}'

Response samples

Content type
application/json
Copy
 Expand all Collapse all
{}

Create Purchase V2 with Agreement Token

This version of the Create Purchase V2 request allows you to process transactions through JumiaPay using an agreement token. For detailed information about how our Purchases feature works, the purchases possible status and how to simulate them, give a look at our Integration Guides.

path Parameters
shopConfigId
required
string <uuid>

Merchant shop configuration id provided by JumiaPay.

header Parameters
apikey
required
string

Fill in with the API key shared by our team

Content-Type
required
string
Example: application/json

The Content-Type (only application/json is supported)

Request Body schema: application/json
description
required
string [ 2 .. 254 ] characters

Brief description of the purchase. This description is for internal use only, it will not be visible to the customer.

amount
required
object

Order amount object

consumer
required
object

Customer's information necessary to create a purchase.

merchant
required
object

Merchant fields object

basket
required
object

Object with product(s) or service(s) data. This data will be shown to the customer in the Cart Detail on JumiaPay website.

expirationTime
integer [ 1 .. 262980 ]

The period of time in minutes provided by the merchant to JumiaPay for the customer to finish his purchase. The customer has 120 minutes if the value is not given by default.

shippingAddress
object

Shipping data to which the products will be delivered.

billingAddress
object

Billing data information.

additionalData
object <= 4096 characters

Additional data with all extra information about the purchase

agreement
object

Agreement data information.

Responses

201

Created

400

Bad Request: The request was unacceptable, due to missing required parameter

401

Unauthorized: Missing or invalid apiKey provided

403

The merchant does not have access to create new purchases.

404

The resource provided was not found

405

HTTP method not supported

422

The request was well-formed but was unable to be followed due to semantic errors

500

Something went wrong while communicating with JumiaPay

post/v2/merchants/ {shopConfigId}/purchases

Sandbox URL

https://api-sandbox-pay.jumia.com.ng/v2/merchants/ {shopConfigId}/purchases

Production Url

https://api-pay.jumia.com.ng/v2/merchants/ {shopConfigId}/purchases

Request samples

Content type
application/json
Copy
 Expand all Collapse all
{
  • "description": "JumiaPay order",
  • "expirationTime": 30,
  • "amount":
    {
    },
  • "merchant":
    {},
  • "consumer":
    {
    },
  • "basket":
    {
    },
  • "shippingAddress":
    {
    },
  • "billingAddress":
    {
    },
  • "additionalData": "{value1: value 1, value2: value 2}",
  • "agreement":
    {
    }
}

Response samples

Content type
application/json
Copy
 Expand all Collapse all
{
  • "purchaseId": "AAEAAADoKU7Uu5tJ9YDGV0bgjb4-siGzk4ackv3oao8qsZH3F1SidiKU",
  • "status": "PENDING",
  • "jpay_trace_id": "42a20463bbec1f35e4c85139691bfc8f"
}

Delete agreement token

A merchant must have the possibility to delete an agreement token from its user

path Parameters
shopConfigId
required
string <uuid>

Merchant shop configuration id provided by JumiaPay.

agreementToken
required
string <uuid>

A unique value generated by you to identify a payment agreement with the payer to be deleted.

header Parameters
apikey
required
string

Fill in with the API key shared by our team

Content-Type
required
string
Example: application/json

The Content-Type (only application/json is supported)

Responses

204

No Content success status response code indicates that a request has succeeded, no action needs to be taken.

401

Unauthorized: Missing or invalid apiKey provided

403

The merchant does not have access to create new purchases.

404

Not found: The endpoint or page requested was not found

405

HTTP method not supported

422

The request was well-formed but was unable to be followed due to semantic errors

500

Something went wrong while communicating with JumiaPay

delete/v2/merchants/{shopConfigId}/agreements/{agreementToken}

Sandbox URL

https://api-sandbox-pay.jumia.com.ng/v2/merchants/{shopConfigId}/agreements/{agreementToken}

Production Url

https://api-pay.jumia.com.ng/v2/merchants/{shopConfigId}/agreements/{agreementToken}

Request samples

Copy

curl -X DELETE 'https://api-staging-pay.jumia.com.ng/v2/merchants/{shopConfigId}/agreements/{agreementToken}' \
--header 'apiKey: <YOUR_API_KEY>' \
--header 'Content-Type: application/json'

Response samples

Content type
application/json
Copy
 Expand all Collapse all
{
  • "message": "No API key found in request"
}

Get one touch agreement details

Retrieve a list of one touch agreements and their data for a certain external request id at a specific shop. If a merchant does not receive a callback after creating an agreement, they can use this API to enquire about its details.

path Parameters
shopConfigId
required
string <uuid>

Merchant shop configuration id provided by JumiaPay.

query Parameters
externalRequestId
required
string <uuid>

External identification provided by merchant to match the agreement token with a user.

header Parameters
apikey
required
string

Fill in with the API key shared by our team

Content-Type
required
string
Example: application/json

The Content-Type (only application/json is supported)

Responses

200

Success

400

Bad Request: The request was unacceptable, due to missing required parameter

401

Unauthorized: Missing or invalid apiKey provided

403

The merchant does not have the feature enabled.

404

The resource provided was not found

405

HTTP method not supported

500

Something went wrong while communicating with the server

get/v2/merchants/{shopConfigId}/agreements/one-touch?externalRequestId={externalRequestId}

Sandbox URL

https://api-sandbox-pay.jumia.com.ng/v2/merchants/{shopConfigId}/agreements/one-touch?externalRequestId={externalRequestId}

Production Url

https://api-pay.jumia.com.ng/v2/merchants/{shopConfigId}/agreements/one-touch?externalRequestId={externalRequestId}

Request samples

Copy
curl -X GET \
  'https://api-staging-pay.jumia.com.ng/v2/merchants/{shopConfigId}/agreements/one-touch?externalRequestId={externalRequestId}' \
  -H 'apikey: <YOUR_API_KEY>' \
  -H 'Content-Type: application/json' \
  -H 'cache-control: no-cache'

Response samples

Content type
application/json
Copy
 Expand all Collapse all
[
  • {
    },
  • {
    }
]

Purchase Status Callback

When a purchase transaction is created, JumiaPay will automatically notify you every time there's a change of its status. To do so, we'll send you a POST request to the purchaseCallbackUrl parameter provided by you on the Create Purchase request.

After receiving this request with success, we expect you to send JumiaPay a success message with status code 200. Otherwise, JumiaPay will keep sending the Callback to you up to 5 times until we get a successful response.

It's very important that you check the Callback request to confirm the transactions status before delivering value to the customer! Note that just because the customer reached your purchaseReturnUrl, it doesn't mean that the transaction is already successful. The transaction should only be considered successful when it reaches the status 'Completed' on JumiaPay side and never before.

Bellow, you'll find a brief explanation of the fields sent on the Callback request.

transactionEvents
Array of objects

List of events for a specific transaction

Copy
 Expand all Collapse all
{
  • "transactionEvents":
    [
    ]
}

Agreement Status callback

When the user finish the process of creating a new agreement, JumiaPay will automatically notify the merchant. To do so, JumiaPay will send HTTP POST request to the callback URL parameter provided by the merchant on the redirect page, where the merchant will send the user to JumiaPay.

If for some reason the callback did not reached your system, JumiaPay will cancel the agreement's creation. The user will be able to try to create another agreement.

Bellow, you'll find a brief explanation of the fields sent on the Callback request if the Agreement creation succeded.

agreementToken
string <UUID>

A unique value generated by you to identify a payment agreement with the payer. You also need to submit it on subsequent merchant-initiated transactions to link payments in a series. This is required to comply with card scheme mandates where the Agreement ID acts as an identifier to link the preceding cardholder-initiated transaction to the subsequent merchant-initiated payments.

externalRequestId
string

External identification provided by merchant to match the agreement token with a user

status
string
Value: "ACTIVE"

Agreement details

  • ACTIVE: The agreement was created successfully
Copy
 Expand all Collapse all
{
  • "agreementToken": "b69ac853-0170-4399-bdda-b3d4834e6b22",
  • "externalRequestId": "externalRequestId",
  • "status": "ACTIVE"
}

Bellow, you'll find a brief explanation of the fields sent on the Callback request if the Agreement is Expired.

agreementToken
string <UUID>

A unique value generated by you to identify a payment agreement with the payer. You also need to submit it on subsequent merchant-initiated transactions to link payments in a series. This is required to comply with card scheme mandates where the Agreement ID acts as an identifier to link the preceding cardholder-initiated transaction to the subsequent merchant-initiated payments.

externalRequestId
string

External identification provided by merchant to match the agreement token with a user

status
string
Value: "EXPIRED"

Agreement details

  • EXPIRED: The agreement is linked to an expired card, so it is marked as expired
Copy
 Expand all Collapse all
{
  • "agreementToken": "b69ac853-0170-4399-bdda-b3d4834e6b22",
  • "externalRequestId": "externalRequestId",
  • "status": "EXPIRED"
}

Bellow, you'll find a brief explanation of the fields sent on the Callback request if the Agreement creation failed.

externalRequestId
string

External identification provided by merchant to match the agreement token with a user

error
object

Error details

Copy
 Expand all Collapse all
{
  • "externalRequestId": "externalRequestId",
  • "error":
    {
    }
}

Error Codes

JumiaPay error codes

Error Code Description
10000 General Error in case of unexpected error in JumiaPay
20110 Invalid fields provided to the JumiaPay
20231 Recurring payments feature is disabled
20232 Merchant does not have access to the feature
20235 Unknown merchant
20271 HTTP method is not supported to the resource
20240 Agreement token does not have access to the feature
20257 Agreement token cannot be deleted
20282 Duplicated merchant refrence identification
20284 Agreement token is not active
20285 Agreement token provided does not match with recurring type

Purchases

Create Purchase Deprecated

This operation has been deprecated and replaced by Create Purchase V2. It is being preserved to ensure backwards compatibility, but you are strongly encouraged to update to our latest APIs. You may find the original documentation below for your reference.

The Create Purchase request allows you to process transactions through JumiaPay.

header Parameters
apikey
required
string

Fill in with the API key shared by our team

Content-Type
required
string
Example: application/json

The Content-Type (only application/json is supported)

Request Body schema: application/json
shopConfig
required
string (ShopConfig)

Merchant token provided by JumiaPay to identify your shop. This parameter can be found on JumiaPay Business, in the ‘ShopConfigurations’ sub-module with the name Shop Key.

priceAmount
required
string

Price amount of the purchase. This amount will be transferred to your business shop wallet.

The priceAmount can have up to 2 decimal places. A decimal point must be used to separate the integer part from the fractional part of the number. Example: 10000.99

priceCurrency
required
string
Enum: "NGN" "EGP" "KES" "GHS" "MAD" "XOF" "TND" "UGX"

Price currency corresponds to official ISO 4217 currency codes:

  • Nigeria: NGN
  • Egypt: EGP
  • Ghana: GHS
  • Kenya: KES
  • Morocco: MAD
  • Ivory Coast: XOF
  • Tunisia: TND
  • Uganda: UGX
merchantReferenceId
required
string <= 255 characters

Merchant’s unique reference id generated by you for the purchase. This is an alphanumeric field with a maximum length of 255 characters.

purchaseReturnUrl
required
string <url>

Return url to the business website once the transaction is created on JumiaPay. This url must be provided by you.

purchaseCallbackUrl
required
string <url>

Purchase callback url to which JumiaPay will send the purchases’ status update. This url must be provided by you.

You may find an example of the request body that JumiaPay will send to you upon callback here.

consumerData
required
object

Customer's data necessary to create a purchase.

basket
required
object

Object with product(s) or service(s) data. This data will be shown to the customer in the Cart Detail on JumiaPay website.

description
string

Brief description of the purchase. This description is for internal use only, it will not be visible to the customer.

shippingAddress
object

Shipping data to which the products will be delivered.

billingAddress
object

Billing data information.

Responses

200

Success

400

Bad Request

401

Unauthorized: Missing Shop Config or API Key

post/merchant/create

Sandbox URL

https://api-sandbox-pay.jumia.com.ng/merchant/create

Production Url

https://api-pay.jumia.com.ng/merchant/create

Request samples

Content type
application/json
Copy
 Expand all Collapse all
{
  • "shopConfig": "YOUR_SHOP_KEY",
  • "priceAmount": "390",
  • "priceCurrency": "NGN",
  • "merchantReferenceId": "<YOUR_UNIQUE_MERCHANT_REFERENCE_ID>",
  • "purchaseReturnUrl": "https://example.com/book/payreturn/5kooig?lastname=Booking",
  • "purchaseCallbackUrl": "https://example.com/purchase_callback",
  • "consumerData":
    {
    },
  • "basket":
    {
    },
  • "description": "Hotel booking",
  • "shippingAddress":
    {
    },
  • "billingAddress":
    {
    }
}

Response samples

Content type
application/json
Copy
 Expand all Collapse all
{}