Create a Mercury payment request
Use “Create a Mercury payment request” in Recued. Validates an explicit funding account, recipient, positive amount, method, and caller-owned idempotency key; fresh-reads both targets; then queues one Mercury send-money request behind Recued approval and Mercury's separate approver policy.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (12 steps)
account_id_trimmed
trim
Trim whitespace from setting account id
recipient_id_trimmed
trim
Trim whitespace from setting recipient id
idempotency_key_trimmed
trim
Trim whitespace from setting idempotency key
has_account_id
compare
Check if account id trimmed has data
has_recipient_id
compare
Check if recipient id trimmed has data
has_key
compare
Check if idempotency key trimmed has data
positive_amount
compare
Check if setting amount is greater than 0
ready
all
Check if all conditions are true
funding_account
?
skip: step.ready not_equal true
recipient
?
skip: step.ready not_equal true
create
?
skip: step.ready not_equal true
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
note
setting
=
[object Object]
amount
setting
=
[object Object]
mercury
setting
=
purpose
setting
=
[object Object]
account id
setting
=
[object Object]
recipient id
setting
=
[object Object]
external memo
setting
=
[object Object]
payment method
setting
=
ach
idempotency key
setting
=
[object Object]
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.