Static templates and memos: one account, many payers

SET API and SET Merchant API · Live since 2026-11-09

A virtual account gives each customer its own account number. When many payers pay one customer, a shared account with a memo can be cheaper: each payer quotes the memo, and SET's provider matches the payment to it. Payments are delivered as stablecoin less SET's fee, as with a virtual account.

Static templates (recommended)

POST /v1/static_templates {customer, currency?, rail?, asset, address, beneficiary | settleTo: {wallet}, reference?, platformFeeBps?}

• A template is a set of standing deposit instructions with no amount: payers send what they owe, quoting memo.
• Every payment that matches becomes its own record (GET /v1/static_template_transfers, event static_template_transfer.<state>). Name who paid with POST /v1/static_template_transfers/{id}/sender.
• GET /v1/static_templates/{id} reads the account number or IBAN live; it is never stored.
• POST /v1/static_templates/{id}/cancel stops new payments. Payments already made carry on.
• The same reference returns the same template, so a retry never opens a second one.

Static memos

POST /v1/static_memos {customer, asset, address, beneficiary | settleTo: {wallet}, platformFeeBps?} opens a shared USD account (wire or ACH push) with a memo.

• SET's provider has superseded static memos with static templates but keeps supporting them. Every answer carries a deprecation note.
• No microdeposit or challenge-deposit verification on a shared account (supportsMicrodeposits: false).
• Find the memo a payer quoted with GET /v1/static_memos?memo=, and its deposits with GET /v1/static_memo_deposits?memo=.

Which to use

Sandbox

POST /v1/sandbox/static_template_transfers and POST /v1/sandbox/static_memo_deposits simulate a payment and move it through its states. No money moves.