Marketplace payouts
Connect approved seller and service-provider payments to your platform records and controls.
Programmable payments
Connect payment intent, permissions, approvals, execution, and status so your product can coordinate supported global money movement without turning every exception into manual work.
Now onboarding design partners.
Use cases
Start with a repeatable operating job and define the controls it needs before money moves.
Connect approved seller and service-provider payments to your platform records and controls.
Move approved payroll funds in controlled groups. Decaf does not calculate wages, taxes, benefits, or employment obligations.
Prepare, validate, approve, and track groups of supplier payments.
Reach recipients through WhatsApp or email and guide them into a secure claim and eligible access journey.
Operational design
The payment lifecycle should preserve intent and make actionable states visible to product and operations teams.
One identity represents one intended operation across safe retries.
Keep submitted instructions and outcomes traceable rather than silently replacing them.
Separate successful, pending, and failed items when a group has mixed outcomes.
Check recipient and route requirements before execution.
Require an authorized approval step where the agreed workflow needs it.
Controlled lifecycle
Each step represents a responsibility in a reviewed integration—not a published endpoint or state enum.
Explore related workflows
See the complete controlled payment platform.
Apply identity, budget, policy, and approval boundaries to agent requests.
Connect the payment lifecycle to supported fiat and USDC infrastructure.
See the Business workflow for controlled recipient batches.
Programmable-payments FAQ
Design-partner access
Tell us the payment job, controls, markets, and outcomes your product needs.
Now onboarding design partners.