Skip to main content
POST
/
merchant
/
invoice
/
external_gateway_invoice
/
update_payment_link
Update External Gateway Invoice Payment Link
curl --request POST \
  --url https://api.unibee.dev/merchant/invoice/external_gateway_invoice/update_payment_link \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "externalTransactionId": "<string>",
  "invoiceId": "<string>",
  "paymentLink": "<string>",
  "signature": "<string>",
  "timestamp": 123,
  "gatewayId": 123,
  "sendInvoice": true
}
'
{
  "code": 123,
  "data": {
    "invoiceId": "<string>",
    "paymentLink": "<string>",
    "status": "<string>"
  },
  "merchantId": 123,
  "message": "<string>",
  "redirect": "<string>",
  "requestId": "<string>"
}

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Update invoice payment link and optionally send email. Auth: OpenAPI + signature (HMAC-SHA256, hex).

externalTransactionId
string<string>
required

External payment transaction id from gateway (for linking)

invoiceId
string<string>
required

Invoice id

External payment/checkout url shown to user in invoice

signature
string<string>
required

HMAC-SHA256(gatewayKey, invoiceId|externalTransactionId|timestamp), hex

timestamp
integer<int64>
required

Request timestamp, UTC seconds, used for expiry check

gatewayId
integer<int64>

Optional. External gateway id; omit to keep current gateway and use it for auth

sendInvoice
boolean<bool>

Whether to (re)send invoice email after payment link is updated

Response

200 - application/json
code
integer<int>
data
object
merchantId
integer<int64>
message
string<string>
redirect
string<string>
requestId
string<string>