Payment writing examples that keep the meaning

A useful edit makes an instruction easier to understand while keeping its payment meaning. Sometimes the right result is a question. Sometimes the original sentence should stay.

These examples illustrate the Atlas Payments English rules. They are editorial examples, not permission to perform a payment operation.

Keep both capture conditions

Preserve permission and conditions
BeforeUpon receipt of an approved authorization, the merchant may capture the payment after the order ships.
AfterIf the authorization is approved and the order has shipped, the merchant may capture the payment.

The merchant, approved authorization, shipped order and permission all remain. Replacing may with must would change the instruction.

Ask what “reverse” means

Clarify an ambiguous operation
InputReverse the payment.
ReviewPAY-03 — Blocker. What is the current payment state, and do you mean cancellation, authorization reversal, or refund?

The editor should not choose an operation from the wording alone. Compare the scoped definitions in the payments glossary.

Separate sequential instructions

One procedural instruction per sentence
BeforeOpen the payment record and read the transaction identifier.
AfterOpen the payment record. Read the transaction identifier.

STYLE-01 separates these sequential actions. It permits actions that occur together to remain in one sentence.

Keep the request separate from the result

The merchant submitted an authorization request.

This sentence can remain unchanged. It says that a request was submitted. It does not establish that the issuer approved it, the merchant captured it, or the funds settled. PAY-01 protects that distinction.

Keep an explicit prohibition

The operator must not retry the declined transaction.

A safe rewrite can retain this sentence. Keep the actor and must not explicit. A request to simplify descriptive text does not require converting it into an imperative.

Make the refund deadline usable

Identify the missing facts
InputRefund the amount within five days.
QuestionsWhat amount and currency should be refunded? What event starts the five-day period? Are these calendar days or business days? Which timezone applies if it affects the cutoff?

Identifying one missing fact does not resolve the others. The editor should ask for the information that changes the instruction rather than invent it.

Preserve exact technical identifiers

If status is requires_capture, the merchant may capture USD 25 by 17:00 UTC on 20 November 2026.

Keep the status value, actor, may, amount, currency, date and time. The example preserves a source instruction; it does not verify that a provider permits that capture or deadline.

Apply the same check to your own text

Compare the actor, state, request or outcome, event order, conditions, obligations, amounts, currency, deadline and identifiers before accepting a rewrite.