APPLICATION INTEGRATION / Agency Agents community
Payments and billing engineer
Models payment mutations, subscriptions and fulfillment as retryable state machines with durable webhook intake and reconciliation.
“Expert payments engineer for PSP integrations (Stripe, Adyen, Braintree, PayPal), idempotent payment flows, webhook processing, subscription billing, SCA/3DS, PCI scope reduction, and financial reconciliation.”
01 / THE REASONING
Why this made the selection.
- The example separates verified event acceptance from leased processing and only marks completion after side effects succeed.
- It names crash boundaries before inbox commit, during pending duplicates and before/after fulfillment; downstream fulfillment still needs its own atomic/idempotent guarantee.
- It treats a charge as retryable only when the idempotency key comes from the business operation, and it fulfills from the processor webhook rather than the browser redirect.
- Amounts are minor-unit integers with a currency code, and the rules include 3DS, disputes, and a daily payout reconciliation instead of a success-card test.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- engineering/engineering-payments-billing-engineer.md (complete definition)
- LICENSE (applicable redistribution terms)
- Host custom-agent documentation; repository installation guidance where applicable
Our findings
- The example separates verified event acceptance from leased processing and only marks completion after side effects succeed. It derives retry keys from the business operation and uses a verified processor-success event, rather than a browser return, to trigger fulfillment.
- It names crash boundaries before inbox commit, during pending duplicates and before/after fulfillment; downstream fulfillment still needs its own atomic/idempotent guarantee.
- Critical rules forbid raw card data on the server and require an idempotency key derived from the order, not a fresh UUID per HTTP call.
- Fulfillment is tied to payment_intent.succeeded or the PSP equivalent, not to the customer landing on a success page.
- There is no tools field. Host documentation says an omitted tools list inherits every tool available to subagents.
- The profile is Markdown to copy into ~/.claude/agents/. It does not register itself, and it does not perform a payment.
Not established by this review
- No agent was installed or invoked. Host/model compatibility, task accuracy and runtime behaviour were not tested.
- The resource was not executed and its tools were not called.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Use the role in your project.
- Read the pinned definition and MIT licence; review the host permissions before use.
- Keep the original unchanged; place a separate working copy with a valid agent slug and supported frontmatter in .claude/agents/, and explicitly configure its tool permissions.
- Provide money/currency flows, processor sandbox, order/ledger schema and refund/subscription policies.
Before you start
- Claude Code or an equivalent role-prompt host
- A scoped application checkout, relevant test data and separately installed toolchains
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/engineering/engineering-payments-billing-engineer.md
Supports: Workflow, inputs and outputs, Declared tools and constraints, Selection and limitations
https://github.com/msitarzewski/agency-agents/blob/bd956db032d907387e6b9ddebff3e18f1de8c679/LICENSE
Supports: Licence and attribution requirements
https://code.claude.com/docs/en/sub-agents.md
Supports: Host setup and permission defaults