菜单
Investigates and resolves a returned Newline banking transfer by tracing the return back to its original transaction and transfer, reviewing the return reason, and checking account balance impact. Use when asked to handle, investigate, or explain a returned payment or ACH return.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Reconciles a Newline synthetic account against its underlying custodial account by comparing balances, synthetic line items, and custodial line items. Use when asked to reconcile, audit, or verify that account balances match across the synthetic and custodial layers.
Creates a Newline banking transfer between two synthetic accounts. Handles all three transfer types: Wire, ACH, and Instant Payment. Use this skill when asked to send money, initiate a transfer, move funds, or create any Wire/ACH/Instant Payment between accounts.
Builds a complete snapshot of a Newline customer, including their profile, KYC status, synthetic accounts and balances, recent transactions, and recent activity. Use when asked to look up, summarise, or report on a customer.
Investigates a Newline banking transfer end-to-end by drilling through the transfer, its transactions, transaction events, any returns, and the combined transfer view. Use when asked to debug, trace, audit, or check the status of a transfer.
General payment initiation workflow for the Newline MCP server. Use when you need to prepare and create a wire, ACH, or instant payment transfer, validate the source and destination accounts, and explain rail-specific requirements. Prefer this skill for end-to-end payment execution across Claude Code, Codex, Pi, and other Agent Skills compatible harnesses.
Broad customer and account management workflow for the Newline MCP server. Use when you need to find customers, assess KYC and status, review pools and products, inspect existing synthetic accounts, or create a new synthetic account. Prefer this skill for multi-step setup and account administration tasks across Claude Code, Codex, Pi, and other Agent Skills compatible harnesses.
| name | return-resolution |
| description | Investigates and resolves a returned Newline banking transfer by tracing the return back to its original transaction and transfer, reviewing the return reason, and checking account balance impact. Use when asked to handle, investigate, or explain a returned payment or ACH return. |
Workflow for understanding and resolving a returned transfer on the Newline platform.
If you have the return UID:
get-return uid=<return_uid>
If you need to find it:
list-returns
Record from the return:
uidoriginal_transaction_uid — the transaction that was returnedreturn_reason — the return reason code or descriptionamount and currencystatus — e.g. pending, processedprocessed_at — when the return was settled (null if still pending)get-transaction uid=<original_transaction_uid>
Record:
synthetic_account_uid — the account affectedtransfer_uid — the originating transfer (if applicable)transaction_type, amount, statuscustodial_account_uidbalance_after — the balance after the original transaction postedIf the transaction has a transfer_uid:
get-newline-transfer uid=<transfer_uid>
Record:
source_synthetic_account_uid and destination_synthetic_account_uidinitiating_customer_uidach, wire, or instant_payment) and its fieldsusd_transfer_amount and statusFor ACH returns the ach.sec_code and return reason code together
identify the specific NACHA return category (e.g. R01 Insufficient Funds,
R02 Account Closed, R03 No Account).
list-transaction-events
Look for events where transaction_uid matches the original transaction UID.
A return event will typically show event_type containing "return" and the
reason in description or metadata.
get-synthetic-account uid=<synthetic_account_uid>
Compare the current net_usd_balance against the balance_after recorded in
Step 2. The difference should reflect the return credit/debit.
Also check the synthetic line items for a return credit entry:
list-synthetic-line-items
Filter for the synthetic_account_uid and look for a line item whose
transaction_uid corresponds to the return (typically created after the
original transaction).
Report: