Start with three separate decisions
Hosting describes who operates the software. Custody describes who can move funds. Settlement describes what asset reaches your business and where. These are different questions: PayIn presents hosted Cloud and self-hosted Open within its non-custodial model.[6] Stripe’s current stablecoin documentation says completed payments settle into a Stripe balance in local currency. The applicable currency depends on the current product and merchant region; USD presentment is not a universal USD settlement rule.[1] Do not infer custody or settlement currency from a deployment label. Write down the destination of funds, the people with signing authority and the operator of the payment monitor before comparing features.
Build a responsibility sheet
Our recommendation is to assign an owner and a backup for node or RPC failures, webhook delivery, key rotation, ledger reconciliation, software upgrades and customer refunds. A hosted arrangement should identify what the provider actually undertakes and what remains with your team. A self-hosted arrangement should name the engineer who can restore a backup and the finance operator who can verify it. If a responsibility has no owner, the architecture diagram is not a launch plan.
Compare costs without a fake price ranking
BTCPay describes open-source software without processing or subscription fees, but also explains that the monitoring software needs hosting and that network fees remain.[5] It is a Bitcoin-oriented reference, not evidence that a particular stablecoin integration exists. Budget your own hosting, monitoring, backups, upgrades, security review and incident response. For a hosted offer, request the actual contract, usage charges, export capability and termination terms. An unpriced operational obligation is not a zero-cost feature.
Run a reversible pilot
Use a sandbox and test orders before exposing a live payment option. Demonstrate that the application survives repeated notifications, missing notifications and a restart during fulfillment. Export enough data to reconstruct one order without relying on a dashboard screenshot. Simulate a provider outage and document how customers see pending payments. These are suggested acceptance exercises, not claims that we performed a payment integration or benchmarked a vendor.
Decision and exit checklist
Choose hosted operation when a named provider covers the operational work you cannot staff and its settlement model fits your needs. Choose self-hosting when control has a concrete purpose and your team can maintain it. Either way, require a documented key boundary, an export format, an incident contact, a recovery rehearsal and a retirement plan for old receiving addresses. Revisit the choice when volume, markets or staffing changes; no provider ranking here substitutes for current commercial and technical due diligence.
Sources & currency
Continue reading
Order payments or deposit addresses? Model the business event first →
All field guides →