Apply credit memo to an order
Applies the credit memo to an open invoice/order as a payment, through the canonical
credit-apply path (same code path as the internal UI): the memo’s balance_remaining
and the account’s spendable credit_balance decrement, an order_payments row is
recorded (method credit), order.balance_due / payment_status recalculate, and
the GL entry posts (DR Customer Credits liability / CR Accounts Receivable).
Refusal guards:
- 409
order_already_fully_paid— target order has zero open balance. Issue an unapplied customer credit instead, or apply to a different open invoice. - 422
apply_amount_exceeds_order_balance— requested apply amount is greater than the order’s current open balance. Reduce the amount and retry. - 400
credit_memo_not_applicable— the memo is voided / expired / fully applied (terminal states are locked). The body includes the memostatus. - 422
amount_exceeds_balance_remaining— requested apply amount exceeds the credit’sbalance_remaining. - 403
credit_memo_account_mismatch— the memo belongs to a different customer account than the target order.
If amount is omitted, the full remaining credit is applied (capped at the order’s
open balance). Industry parity: NetSuite + Acumatica + QuickBooks all refuse
credit-to-fully-paid; Arcus matches that behavior.
Authorizations
API key issued per entity via Settings > Developers > API Keys.
Each key carries scopes (e.g. orders:read, products:write).
Bearer token format: Authorization: Bearer ark_live_ent_Test keys use ark_test_ent_. Both are issued per entity
via Settings > Developers > API Keys.

