Outbound: Payment status change

Direction: Outbound (BNPL WL → Partner). This is NOT a callable API endpoint — it documents the payload we send to your configured webhook_url.

Sent to your webhook_url when a payment is confirmed or fails. A single payment may cover installments from multiple orders (applications). The order_references array lists all affected orders. Note: One payment.status_change event is dispatched per batch payment (one boleto/PIX transaction), regardless of how many invoices are covered. Use invoice.status_change to track per-invoice state changes. Note: The payment provider may use a CONFIRMED state internally (boleto/PIX issuance acknowledged), but this is never exposed to partners. From the partner perspective, payment status is either PENDING or PAID.

Headers sent:

HeaderDescription
Content-Typeapplication/json
X-Webhook-Signaturebase64url ECDSA signature of the body (verify with our public key)

Your endpoint must:

  • Return HTTP 2xx within 10 seconds
  • Be idempotent (you may receive the same event more than once)
Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
enum

Event type identifier

Allowed:
string

Unique payment identifier

string | null

Payment reference from the partner (if provided during charge)

string
enum

Payment status. PENDING = boleto/PIX emitted, awaiting payment. PAID = payment received.

Show Details
PENDINGPayment created, awaiting confirmation
PAIDPayment confirmed and settled
EXPIREDPayment expired (TTL passed without confirmation)
FAILEDPayment processing failed
CANCELLEDPayment cancelled
Allowed:
double

Payment amount

string
enum

Payment method used

Allowed:
order_references
array of objects

List of orders (applications) affected by this payment

order_references
date-time

Timestamp when the payment was processed

string

Base64url ECDSA-P521-SHA256 signature of the request body. Identical to the X-Webhook-Signature header — included in the body as a convenience for partners whose infrastructure strips custom headers.

Response
200

Your endpoint should return HTTP 2xx to acknowledge receipt

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here!