Global payments teams need a shared language

The short answer

Clear payment writing makes actors, states, conditions and obligations explicit. Atlas Payments English combines 255 scoped terminology entries with four review rules and two editing modes, helping teams review wording without silently changing payment meaning.

In this article
  1. What Wittgenstein’s language-games have to do with payments
  2. Why global teams need more than simpler sentences
  3. What is included in Atlas Payments English?
  4. How do the four rules work?
  5. What happens when you submit text to the editor?
  6. What has actually been tested?
  7. How should a team start using it?

“The payment is approved.” Five familiar words can still leave room for misunderstanding.

The checkout team may be describing an authorization response. The operations team wants to know whether a capture succeeded. Finance is looking for settlement. Support needs to explain what the customer should expect next. Those questions belong to the same payment, but they ask about different events.

Those teams may work in different countries, across languages and timezones. Provider-specific status values and network terminology add complexity. So does a handover written at the end of a long shift. A fluent sentence can still leave the next person uncertain about the event or required action.

That is the problem I want Atlas Payments English to help with: making payment documentation clearer while preserving the details that determine its meaning.

What Wittgenstein’s language-games have to do with payments

In Philosophical Investigations, §43, Ludwig Wittgenstein writes:

“the meaning of a word is its use in the language”

He qualified that observation as applying to a large class of cases, rather than every use of the word “meaning.” His idea of a language-game connects language with the activities in which people use it. The Stanford Encyclopedia of Philosophy discusses that context.

I find the connection useful in payments. An engineer reading an API response, an operator following a refund procedure and a finance team matching a payout are using language within different activities. A word such as “complete” needs the relevant event and context before another team can act on it.

A controlled writing profile makes the chosen use explicit for a particular document. It does not establish one universal meaning for every provider, network or situation. The practical question is: what does this word mean here, and what action follows from it?

Why global teams need more than simpler sentences

Shared language helps native and non-native English speakers alike. The task is to make the instruction usable across roles, locations and working hours. A reader should be able to identify the actor and payment state. The required conditions and next event should also be clear.

Consider “Refund the amount within five days.” A shorter version would not supply the missing amount, currency or deadline basis. Five calendar days after a customer request can produce a different cutoff from five business days after approval. If a timezone changes the cutoff, it must also be supplied.

Clear source text gives translation and localization reviewers more explicit information. The editor itself does not certify translations or guarantee that every reader will understand a document. Global teams still need local context, agreed terminology and a way to ask questions.

What is included in Atlas Payments English?

The public 0.2.1 editing profile combines a payments glossary, a short rulebook and examples. The published reference set contains the following:

The published editing profile
ComponentCountWhat the count means
Payment terminology entries255Scoped definitions with recommended usage and public sources.
Single-word headwords56Entries whose term label is written as one word.
Multiword terms199Entries such as authorization request and acquirer reference number.
Stable review rules4STYLE-01 and PAY-01, PAY-02 and PAY-03.
Editing modes2Review and Rewrite.

The 56 headwords and 199 multiword terms together make up the 255 entries. They are Atlas editorial terminology proposals, not 255 ASD-approved words and not a complete general-English dictionary. A term’s definition, source and intended use matter more than the size of the list.

You can read the full payments glossary on this site. Each entry shows its recommended usage and source edition. Readers can check whether that meaning applies.

How do the four rules work?

STYLE-01 applies selected principles from ASD-STE100 Issue 9. Procedures use the imperative and normally put one instruction in each sentence. The sentence limits are 20 words for procedures and 25 for descriptive text, using the standard’s counting rules. Those limits do not justify changing a permission into a command.

PAY-01 protects the actor, payment state and event order. A merchant submitting an authorization request does not establish that the issuer approved it. Authentication, authorization, capture, clearing and settlement need their own context.

PAY-02 protects conditions, explicit modal words, amounts, currencies, deadlines and exact identifiers. May and must carry different obligations. A status value such as requires_capture must not be casually renamed to make a sentence sound smoother.

PAY-03 asks a focused question when a missing fact changes the instruction. “Reverse the payment” requires the current state and intended operation. The editor should not silently choose cancellation, authorization reversal or refund.

The STYLE rule draws on selected ASD writing principles. The PAY rules are Atlas requirements for editorial preservation. This separation lets a reviewer see which standard is being applied.

What happens when you submit text to the editor?

The installed plugin supplies instructions and reference files to your selected model host. The host reads your text and applies the editing profile. It is not a deterministic parser that can prove two sentences have the same meaning.

Review is the default. It returns a quoted excerpt, rule ID, issue, severity and suggested edit. It asks questions when facts are missing and identifies checks it could not complete. A clear sentence should not acquire an invented violation simply to fill a table.

Rewrite is explicit. Ask for a rewrite when you want revised text. The editor returns that text and any questions that still affect meaning. An unresolved passage stays intact until its meaning can be clarified.

Here is the central example:

A clearer capture statement
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 rewrite puts the conditions first. It preserves the merchant, the approved authorization, the shipped order and may. A rewrite that drops the authorization condition or substitutes must fails the payment-meaning check even if it sounds more direct.

More examples, including ambiguous refunds and exact status values, are in the payments writing examples.

What has actually been tested?

The public 0.2.1 skill passed 20 live Codex acceptance cases after fixes to explicit modal preservation and refund clarification. The final answers and tool traces were reviewed. Its 27 local regression tests also passed. Claude Code passed structural plugin and marketplace validation; its model acceptance cases remain unrun.

Those results describe a finite regression suite. They do not establish a reliability percentage across all payment documents, full Issue 9 conformance, current network permission or legal correctness. The public verification record explains the evidence and its limits.

How should a team start using it?

Start with a small, non-sensitive document that several teams already use. Examples include a refund procedure, an incident handover or an API explanation. Ask the editor to Review it before requesting a rewrite. Have the document owner resolve the questions. Have that owner approve consequential changes.

Check the proposed wording against the applicable provider or network source. Keep exact identifiers. Record which terminology choices your team accepts. A disagreement over a word is useful information when it reveals different assumptions about the process.

Use synthetic or redacted material. Do not submit live card data, authentication data, credentials or customer records. The selected host processes text under its own policies. The plugin includes no payment execution, MCP server, telemetry or billing.

Install Atlas Payments English in Codex or Claude Code, or inspect the open-source files on GitHub. The public package is available under MIT; official OpenAI and Anthropic directory listing is not claimed.

If your team needs help agreeing terminology across procedures and systems, discuss a documentation review with Danish. Make the intended meaning explicit before someone has to act on it.

Payment optimization
DS

Danish Siddiqui

Independent payments practitioner with 6+ years in payment orchestration and experience helping 400+ merchants and platforms evaluate, onboard, and optimize payment infrastructure. Atlas of Payments is not owned, funded, or sponsored by a payment orchestration platform.