AnySpend Payment Received

Trigger Commerce

Triggers when a payment completes via AnySpend. Set a destination chain and recipient address to start your workflow when funds arrive.

At a Glance

Field	Value
Trigger ID	anyspend
Category	Commerce
Tags	payment, cross-chain, anyspend

Trigger Configuration

Field	Type	Required	Description
chainId	integer	Yes	Destination chain ID for the payment
recipientAddress	string	Yes	Payment recipient address (hex)
tokenAddress	string	No	Destination token address. If omitted, any token is accepted.
amount	string	No	Required payment amount in token base units (wei).
enablePaymentLink	boolean	No	When enabled, a shareable payment link URL is auto-generated on workflow publish.

Trigger Result

Field	Type	Required	Description
triggeredAt	string	Yes	Timestamp when the payment callback was received (UTC, RFC3339 format)
payment	object	Yes	Payment details from AnySpend
inputs	object	No	Optional form data passed via callbackMetadata
paymentLinkUrl	string	No	The shareable payment link URL (only present for payment-link-enabled triggers)

Workflow Root Example

json
{  "nodes": {    "root": {      "type": "anyspend",      "payload": {        "chainId": 8453,        "recipientAddress": "0x0000000000000000000000000000000000000000"      },      "children": [        "log_event"      ]    },    "log_event": {      "type": "log",      "payload": {        "message": "Triggered at {{$trigger.triggeredAt}}"      },      "children": []    }  }}

Downstream nodes can use {{$trigger.triggeredAt}} and any result fields listed above. Event triggers usually expose the raw source payload under a field such as event, body, trade, or raw.