Skip to main content
POST
Receive a Meld webhook event

Headers

meld-signature
string | null
meld-signature-timestamp
string | null
X-Timestamp-Format
string

Controls how timestamp fields are serialized in JSON response bodies.

Default (header omitted or any other value): epoch milliseconds as integers. iso8601: UTC ISO 8601 strings of the form YYYY-MM-DDTHH:MM:SSZ.

Example: with X-Timestamp-Format: iso8601, the field value 1704067200000 becomes "2024-01-01T00:00:00Z".

Affected fields (recursively, in dicts and arrays): any field whose name ends in _at, plus the literal field names timestamp, period_start, and period_end. All other fields are passed through unchanged.

Only iso8601 is recognized. Any other value (or omitting the header) yields the default epoch-ms representation; the server does not reject unknown values, so this is documented as an example rather than an enum to keep generated clients permissive.

Example:

"iso8601"

Body

application/json
eventType
string
required

Meld event type (e.g. TRANSACTION_CRYPTO_COMPLETE).

eventId
string
required

Unique identifier for the webhook delivery.

timestamp
string
required

Provider-emitted event timestamp.

payload
MeldWebhookEventPayload · object
required

Inner payload of a Meld webhook event for ramp transaction lifecycle.

Captures the documented fields Meld sends in the payload envelope for TRANSACTION_CRYPTO_* events. Marked extra="allow" so future Meld fields are preserved without breaking parsing. Fields are optional except paymentTransactionId, which always identifies the ramp transaction.

Response

Webhook received