What is payment-operations?

A workflow for investigating what happened after a payment transfer was created, including failures, returns, transaction events, and related records.

Use it to inspect transfers, transactions, and returns, reconcile connected records, explain failures, and decide whether a retry needs confirmation.

It helps trace a payment by its identifier instead of guessing whether it should have settled or why it failed.

payment-operations — Skill for Claude Code and Codex by newline53

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add newline53/newline-mcp-server --skill payment-operations

Clone the repo

git clone --depth 1 https://github.com/newline53/newline-mcp-server

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/newline53/newline-mcp-server/payment-operations/github.svg)](https://agentmods.dev/skills/newline53/newline-mcp-server/payment-operations)

Your own site

<a href="https://agentmods.dev/skills/newline53/newline-mcp-server/payment-operations"><img src="https://agentmods.dev/badge/skills/newline53/newline-mcp-server/payment-operations/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/newline53/newline-mcp-server/payment-operations"><img src="https://agentmods.dev/badge/skills/newline53/newline-mcp-server/payment-operations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 895 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00071	$0.00895
Opus 5.5	$0.00028	$0.00358
Sonnet 5.5	$0.00014	$0.00179
Haiku 4.5	$0.00007	$0.00089

Measured 2mo ago against content hash 72a387e71dcf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

payment-operations scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/payment-operations/SKILL.md · 160 lines

How it starts

The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Payment Operations

A general operations skill for transfer follow-up, exceptions, and issue resolution. Use this when the user is asking what happened after a payment was created.

Guardrails

Do not assume a newly created transfer should already be settled.
Investigate by UID whenever possible: transfer UID, transaction UID, return UID.
Use returns and transaction events to explain failures before suggesting retries.
If remediation would require creating another transfer, get user confirmation first.

Step 1 — Start from the Best Identifier Available

If you have a transfer UID

get-newline-transfer  uid=<transfer_uid>

If you have a transaction UID

get-transaction  uid=<transaction_uid>

If you have a return UID

get-return  uid=<return_uid>

If you only have rough context

Use list endpoints to find the right record:

list-newline-transfers
list-transactions
list-returns
list-combined-transfers

Step 2 — Inspect the Transfer Record

From the transfer, capture:

uid, status, created_at
source_synthetic_account_uid
destination_synthetic_account_uid
initiating_customer_uid
destination_customer_uid
usd_transfer_amount
transaction_uids
which rail block is populated: wire, ach, or instant_payment

If there is no transfer, continue from the transaction or return path instead.

For each related UID:

get-transaction  uid=<transaction_uid>

Record:

status
transaction_type
amount, currency
synthetic_account_uid
custodial_account_uid
transfer_uid
balance_after
timestamps and description

If you need broader context:

list-transactions  transfer_uid=[<transfer_uid>]

Step 4 — Inspect Transaction Events

list-transaction-events

Filter for events tied to the transaction UID(s). Focus on:

settlement progress
failure states
return-related events
timing gaps between queued, pending, and settled states

Read the full file on GitHub · 160 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 160 lines · 71 tokens per session scan A 72a387e71dcf

Subscribe to this mod's changes

payment-operations is a skill published in the GitHub repository newline53/newline-mcp-server (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 71 tokens to every session and 895 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Finance and fintech embedded-finance mcp mcp-server newline

payment-operations next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
payment-operationsnewline53/newline-mcp-server	Skill	2	6mo ago	Apache-2.0	A	71	Claude Code, Codex
surfBlockRunAI/blockrun-mcp	Skill	389	today	MIT	A	110	Claude Code, Codex
ib-trades-historystaskh/trading_skills	Skill	404	3d ago	MIT	A	59	Claude Code
scanner-pmccstaskh/trading_skills	Skill	404	3d ago	MIT	A	63	Claude Code
ib-collarstaskh/trading_skills	Skill	404	3d ago	MIT	A	30	Claude Code
ib-portfolio-action-reportstaskh/trading_skills	Skill	404	3d ago	MIT	A	49	Claude Code
calendarstaskh/trading_skills	Skill	404	3d ago	MIT	A	79	Claude Code