Skip to main content
POST
/
public
/
webhooks
/
notify
Notify transaction update
curl --request POST \
  --url https://prod-api.pcxpay.com/v1/public/webhooks/notify \
  --header 'Authorization: <authorization>' \
  --header 'Content-Type: application/json' \
  --header 'X-Api-Key: <x-api-key>' \
  --data '
{
  "org_id": "<string>",
  "transaction_data": {
    "transaction_id": "txn_abc123",
    "status": "completed",
    "amount": 500,
    "currency": "USD",
    "updated_at": "2024-01-15T10:30:00Z"
  }
}
'
{
  "status": "success",
  "message": "Operation completed successfully",
  "data": {}
}

Documentation Index

Fetch the complete documentation index at: https://docs.pcxpay.com/llms.txt

Use this file to discover all available pages before exploring further.

Headers

​
Authorization
string
default:NONE
required

Bearer JWT for user-facing flows (Bearer eyJraWQ...), or the literal string NONE when authenticating via API key.

Example:

"Bearer eyJraWQ..."

​
X-Api-Key
string
default:NONE
required

API key for server-to-server flows, or the literal string NONE when authenticating via JWT.

Example:

"pcx_abc123_xxxx"

Body

application/json
​
org_id
string
required

Organisation whose registered webhooks should receive the notification

​
transaction_data
object
required

Arbitrary transaction payload to forward to the registered webhook endpoint(s). Typically includes transaction_id, status, amount, currency, and relevant timestamps.

Example:
{
  "transaction_id": "txn_abc123",
  "status": "completed",
  "amount": 500,
  "currency": "USD",
  "updated_at": "2024-01-15T10:30:00Z"
}

Response

Notifications dispatched

​
status
enum<string>
Available options:
success,
error
Example:

"success"

​
message
string
Example:

"Operation completed successfully"

​
data
object