Recipes
Each recipe is a sequence of API calls you can run in test mode with your own API keys. Every step shows one request with the current API version (X-Moov-Version: v2026.07.00) and links to the guide that covers that step in depth. If you haven't made an API call yet, start with the quick start and the glossary, which explains accounts, sources, payment methods, and transfers.
Onboard a merchant, link a customer's card, charge it, and track the payment with webhooks.
Link and verify a recipient's bank account, then pay out with ACH or instant payments (RTP or FedNow).
Check a wallet balance, fund it with an ACH debit, pay out from it, and automate settlement with sweeps.
Register an endpoint, verify signatures, process events once, and react to transfer status changes.
Choose between a cancellation, refund, or reversal for card and ACH payments, and track the outcome.
Before you start
All recipes assume you have:
-
A Moov account in test mode. Sign up if you don't have one.
-
An API key. Recipes run on your server, so every request uses Basic authentication with your public and secret key, which doesn't need scopes, plus the API version:
-u "{publicKey}:{secretKey}" \ -H "X-Moov-Version: v2026.07.00"Never send your secret key from a browser or mobile app. Client-side code such as Moov.js and Drops uses access tokens instead; see authenticate API requests.
-
To use an SDK instead of cURL, install it from SDKs and create a client with your public key as the username and your secret key as the password. Each recipe step shows only the call, using this client:
import { Moov } from "@moovio/sdk"; const moov = new Moov({ security: { username: "", password: "", }, });from moovio_sdk import Moov from moovio_sdk.models import components with Moov( security=components.Security( username="", password="", ), ) as moov:require 'moov_ruby' Models = ::Moov::Models s = ::Moov::Client.new( security: Models::Components::Security.new( username: '', password: '' ) )Moov sdk = Moov.builder() .security(Security.builder() .username("") .password("") .build()) .build();using Moov.Sdk; using Moov.Sdk.Models.Components; using Moov.Sdk.Models.Requests; var sdk = new MoovClient(security: new Security() { Username = "", Password = "", });declare(strict_types=1); require 'vendor/autoload.php'; use Moov\MoovPhp; use Moov\MoovPhp\Models\Components; use Moov\MoovPhp\Models\Operations; $sdk = MoovPhp\Moov::builder() ->setSecurity( new Components\Security( username: '', password: '', ) ) ->build(); -
Your partner account ID; see find your account ID. Transfers are created under the partner account, so
POST /accounts/{accountID}/transfersuses your partner account ID. -
A webhook endpoint, or a plan to poll. Recipes point out which webhook events to listen for at each stage.
Onboard & accept card payments
Create a business account, enable collect-funds.card-payments, link a customer's card, create a card transfer, and track it with webhooks.
Pay out to a bank account
Create an individual account, link and verify a bank account, pick a payment method, pay out with ACH or instant payments, and handle returns.
Fund and spend from a wallet
Check a Moov wallet balance, fund it with an ACH debit from a verified bank account, pay out from the wallet, and automate it with sweeps.
Handle webhooks end to end
Register a Moov webhook endpoint, verify signatures, respond fast, dedupe events by ID, react to transfer statuses, and test it.
Refund, reverse, or cancel a payment
Choose between cancel, refund, and reversal for card and ACH payments, call each endpoint, issue partial refunds, and watch the webhooks.