PayOps documentation
Everything you need to detect finalized stablecoin transfers, match the right invoice, deliver signed events, and keep evidence your finance team can trust.
npm install @payops/sdkThe aim
Receiving a stablecoin transfer is easy. The difficult part is proving what that payment was for with enough confidence to update an invoice, release an order, and satisfy finance.
Wallet activity does not carry your complete business context. Teams often compare signatures, recipients, token mints, amounts, references, and finality by hand. Different services then repeat that interpretation and can disagree about whether an invoice is actually paid.
PayOps creates one inspectable payment truth. It records the exact invoice expectation, observes finalized Solana transfer facts, applies deterministic matching rules, and preserves the decision with replayable evidence before notifying downstream systems.
Target audience
PayOps serves teams that accept Solana stablecoins and need the payment record to remain consistent across product, operations, and finance.
Replace wallet-explorer searches and spreadsheet matching with a durable answer for every invoice: paid, still open, or waiting for review.
Give checkout, order, customer, and notification workflows one signed payment event instead of making every service interpret chain data.
Operate a read-only pipeline with replayable parsing, transactional decisions, bounded delivery retries, and inspectable production controls.
End-to-end model
Four explicit boundaries turn a public chain transfer into a business event your systems can safely consume.
Issue an invoice with the supported mint, settlement recipient, exact integer amount, reference, and expiry.
Read the Solana transaction without custody or signing authority and preserve the canonical transfer representation.
Compare immutable expectations with finalized facts. Exact matches become paid; uncertainty becomes an exception.
Store the decision and evidence atomically, then deliver the exact signed lifecycle event with bounded retries.
Deliberately narrow: PayOps does not create wallets, custody funds, sign transactions, quote exchange rates, or replace your accounting system. It gives those systems a reliable reconciliation result and the evidence behind it.
Connect invoice creation, finalized Solana ingestion, deterministic reconciliation, and signed lifecycle events without handing PayOps a private key.
Read guide Understand the pipelinePayOps separates chain ingestion, canonical transfer facts, reconciliation decisions, delivery, and operator review so every decision can be reproduced.
Read guide Consume signed eventsUse a small, versioned event contract for paid invoices and payment exceptions, with canonical bytes and replay-safe identifiers.
Read guide Review the boundariesPayOps is read-only and non-custodial. It validates finalized chain data, fails closed on ambiguity, and signs outbound events without exposing secrets.
Read guideDocumentation path
Start with the working path, then go deeper into architecture, events, security, package boundaries, and the API surface as your integration grows.
Install the SDK, define an invoice, and turn a finalized USDC or USDT transfer into a deterministic payment decision.
Connect invoice creation, finalized Solana ingestion, deterministic reconciliation, and signed lifecycle events without handing PayOps a private key.
PayOps separates chain ingestion, canonical transfer facts, reconciliation decisions, delivery, and operator review so every decision can be reproduced.
Use a small, versioned event contract for paid invoices and payment exceptions, with canonical bytes and replay-safe identifiers.
PayOps is read-only and non-custodial. It validates finalized chain data, fails closed on ambiguity, and signs outbound events without exposing secrets.
Seven Apache-2.0 npm packages published as PayOps v0.1.0 cover contracts, verification, ingestion, reconciliation, webhooks, SDK access, and reference fixtures.
Create customers and invoices, manage settlement wallets, review exceptions, export evidence, and monitor production readiness through versioned HTTP endpoints.