Skip to main content
POST
Deactivate Payment Link

Overview

Closes an active payment link so the buyer can no longer pay through it. The call takes no body, and a successful one returns an empty data:

Path Parameters

  • link_id: The link’s ID from Create Payment Link, e.g. PR4829301756. The payment_id it returned is the same value.
PSPs send X-Merchant-ID naming the sub-merchant the link belongs to, as on Create Payment Link.

What deactivation does

  • The link reads expired. There is no separate deactivated status: deactivating sets expiry_date to the moment of the call, so Retrieve Payment Link and List Payment Links report it as expired, with that moment as its expiry_date.
  • It cannot be undone. To collect again, create a new link with a new reference_id.
  • A payment already underway can still land. If the buyer was mid-payment when you deactivated, check the link afterwards: paid outranks expired, so a link whose payment went through reads paid.

When it is refused

Only an active link can be deactivated. A link that is already paid, expired (deactivated links included) or failed is refused with a 400, so deactivating a link twice fails the second time:

Errors

Authorizations

X-Client-ID
string
header
required

Client Application ID - Your unique application identifier used to authenticate API requests. You can find your Client ID in the Developer Settings section of the merchant dashboard.

X-Client-Secret
string
header
required

Client Secret Key - Your secret key used alongside the Client ID for secure authentication. Keep this confidential and never expose it in client-side code. Available in the Developer Settings section of the merchant dashboard.

X-Merchant-ID
string
header
required

Merchant Identifier - The unique ID for the merchant account. This is required for PSP (Payment Service Provider) merchants who manage multiple merchant accounts. You can find merchant IDs in the Merchant Management section of the dashboard.

X-API-Version
string
header
required

API Version - Specifies which version of the API to use (e.g., '1.X.X', '2.X.X', or '3.X.X'). This header allows you to control which API version your integration uses. Default version information is available in the Developer Settings.

Path Parameters

The link's link_id, as returned by Create Payment Link (PR followed by 10 digits). The payment_id Create Payment Link returns is the same value.

Example:

"PR4829301756"

Response

Payment link deactivated

success
boolean
required

Indicates if the request was successful

message
string
required

Response message

data
object
required

Always empty