Infrastructure
Select and prepare VPS or dedicated infrastructure around stores, node requirements and expected growth.
SELF-HOSTED PAYMENTS
Self-hosted
crypto payment gateway.
WebCare360 sets up your gateway on VPS or dedicated infrastructure, connects your store and configures a merchant-controlled wallet connection. Your business operates the checkout environment after handoff.
Scoped setup & integrationMerchant wallet control
01 / THE SHORT ANSWER
What is a self-hosted crypto payment gateway?
It is a payment application running for your business, connected to your store and wallet configuration. WebCare360 deploys and configures BTCPay Server as the underlying free, open-source platform on VPS or dedicated infrastructure selected for your requirements. We provide infrastructure and setup; the standard deployment connects a merchant-controlled wallet without requiring us to retain signing secrets.
- Service
- Deployment & integration
- Infrastructure
- VPS or dedicated
- Wallet
- Merchant-controlled connection
- After handoff
- Customer-operated gateway
02 / HOW YOUR PAYMENT FLOW WORKS
Your checkout. Your gateway. A clear payment path.
The customer chooses crypto at checkout. Your gateway coordinates the invoice, then monitors payment on the configured network. The store receives the resulting payment status so you can manage the order.
Payment detection, confirmation and completion are different stages. Funds follow the agreed merchant-controlled wallet model; WebCare360 is not a node through which each payment passes.
DNS, hosting, the payment network and selected integrations remain technical dependencies.
03 / WHAT WEBCARE360 SETS UP
From infrastructure selection to a tested handoff.
Gateway deployment
Install the payment platform and establish its base configuration for your agreed deployment.
Domain & TLS
Configure the domain and HTTPS/TLS where included in the agreed setup.
Store configuration
Configure the gateway store and connect the agreed merchant-controlled wallet model.
Commerce integration
Connect the agreed ecommerce integration and review permissions and payment notifications.
Testing & handoff
Test the initial payment flow, then hand over access and the agreed operating responsibilities.
04 / YOUR GATEWAY, YOUR WALLET CONTROL
Keep signing and recovery in your hands.
The standard wallet connection
The gateway observes payment activity using the agreed merchant-controlled wallet configuration. WebCare360 does not request or retain your recovery seed, private keys or signing secrets for this setup.
Your recovery responsibility
You protect the seed, signing device and wallet access, and maintain a recovery plan. A server backup is not a substitute for wallet recovery material.
Do not send your recovery seed or private key through ordinary support channels.
A server-generated hot wallet can expose signing material to a server administrator. It is not the basis of the standard wallet-control model. Lightning or another requested architecture needs its own agreed access and recovery scope.
05 / STORE, API & WEBHOOK INTEGRATIONS
Connect checkout to payment status.
Commerce plugins connect the store to your gateway. APIs let applications create or query payment records; webhooks notify them of payment events.
Integration permissions, event verification and checkout testing belong in the agreed setup. Bespoke development is separate scope, not an automatic inclusion.
| Platform | Integration type | Scope to confirm |
|---|---|---|
| WooCommerce | Documented ecommerce plugin | Plugin, WordPress and store compatibility reviewed before setup. |
| Drupal Commerce | Documented module | Current documentation labels the module alpha; suitability requires review. |
| Magento | Documented ecommerce integration | Extension and Magento version must be checked against the deployment. |
| PrestaShop | Documented ecommerce module | Confirm module/runtime compatibility and checkout behavior. |
| Custom application | Greenfield API / webhooks | Platform capability. Any bespoke development requires separate agreement. |
These are documented platform integrations, not a guarantee that every store version is supported. Confirm the exact method before deployment. Other ecosystem integrations and plugins require their own review.
06 / PAYMENT METHODS & PLATFORM CAPABILITIES
A Bitcoin foundation. Options selected deliberately.
Core gateway capability
Bitcoin on-chain payments, merchant invoices and payment-status tracking are supported by the underlying platform. The configured wallet and confirmation policy determine the payment flow.
Optional platform capability
Lightning support, payment buttons, Point of Sale and payment requests can be considered where useful. Lightning requires its own node/service, liquidity, access and recovery decisions.
Integration-specific capability
Commerce plugins, APIs and webhooks depend on the selected store and application. Additional assets need deployment-specific validation; no additional coin or network is included by default.
Platform support does not mean every option is configured in your deployment. Choose the methods needed for your business.
07 / SELF-HOSTED VS HOSTED PROCESSOR
More control brings more operating responsibility.
Compare the service model, not a universal winner. Security, privacy, reliability and cost depend on the actual architecture and contract.
| Responsibility | Self-hosted gateway | Hosted processor |
|---|---|---|
| Infrastructure control | Your selected server and gateway environment | Service environment and access depend on provider |
| Wallet / custody | Merchant-controlled wallet in the standard setup | Custodial or non-custodial model varies by provider |
| Software maintenance | Customer after handoff, unless separately agreed | Provider generally operates its platform; store integration still needs an owner |
| Processor fee model | No processing percentage imposed by the underlying software; service costs separate | Provider pricing and contract determine charges |
| Network fees | May apply for the chosen payment path | May also apply; inclusion varies |
| Data handling | Merchant manages application data and access | Collection, access and retention follow provider terms |
| Integration flexibility | Documented plugins or separately scoped API work | Available integrations and API access vary |
| Availability responsibility | Infrastructure and application responsibilities must be assigned | Provider service commitments and merchant dependencies both matter |
| Compliance responsibility | Merchant determines applicable obligations | Merchant obligations remain alongside provider requirements |
08 / SECURITY & OPERATIONAL RESPONSIBILITY
Know where setup ends and operation begins.
The baseline service is deployment and initial testing. Ongoing gateway management, transaction monitoring, refunds and store operation are not included by default. Any additional management must be explicitly agreed.
| Layer | WebCare360 setup role | Customer / agreed service role |
|---|---|---|
| Server / OS | Prepare the selected infrastructure | Operate and patch unless the infrastructure agreement assigns another owner |
| Gateway application | Deploy and configure | Maintain application access and configuration after handoff |
| Domain / TLS | Configure where agreed | Maintain domain control and certificate renewal responsibility |
| Store integration | Connect and initially test the agreed method | Operate the store and validate changes to checkout |
| API / webhook credentials | Configure the agreed integration permissions | Protect, rotate and revoke credentials as needed |
| Wallet / keys | Connect the agreed merchant-controlled model | Retain signing, seed protection, access and recovery |
| Backups | Confirm coverage under the selected service | Maintain any uncovered backups and separate wallet recovery |
| Application / plugin updates | Deliver the agreed deployment profile | Own updates and compatibility testing unless separately agreed |
| Monitoring | Agree infrastructure/service coverage | Application and payment-state monitoring are not included by default |
Security depends on patching, authentication, TLS, credentials, plugin quality and recovery. Self-hosting alone does not establish security.
09 / FEES, CONFIRMATIONS & PAYMENT FLOW
Separate the software from the cost of running it.
| Cost category | What to account for |
|---|---|
| Gateway software | Free, open-source software with no imposed processing percentage. |
| Infrastructure | VPS or dedicated hosting has its own recurring cost. |
| Setup & integration | Priced by deployment scope; request a quote for the agreed work. |
| Payment network | Network and payment-path fees may apply, including to refunds. |
| Additional work & services | Any separately agreed management, development or third-party components have their own scope and costs. |
Payment timing
On-chain confirmation and Lightning payment behavior differ. Invoice expiry and the configured payment policy also matter. A detected payment is not a universal promise of immediate completion.
Refund decisions
The underlying platform provides refund tooling. The merchant decides and authorizes refunds under the agreed wallet model; network fees and consumer obligations may still apply.
10 / DEPLOYMENT REQUIREMENTS
Bring the requirements. Agree the deployment.
Infrastructure & growth
Number of stores, expected volume, node needs and the infrastructure you are considering.
Domain & access
Domain/TLS requirements and the authorized store/server access needed for agreed setup.
Wallet & payment methods
A merchant-controlled wallet connection and the payment paths you want reviewed. Do not send signing secrets.
Validation & handoff
Integration requirements, a testing window, backup coverage and named operating owners.
Deployment time depends on infrastructure, wallet/payment methods and integration scope. Resource requirements are selected for the final profile, not a fixed universal minimum.
Start with a VPS
A VPS can suit many initial deployments. Size it for the gateway, node requirements, store volume and growth.
Choose dedicated infrastructure
Consider dedicated resources for heavier or specialized requirements and greater infrastructure control. It is not automatically the better fit for every store.
11 / MERCHANT RESPONSIBILITY & COMPLIANCE
Infrastructure control does not remove business obligations.
Your business responsibilities
WebCare360 provides technical deployment and infrastructure. The merchant determines and meets applicable legal, regulatory, tax, accounting, consumer, sanctions and KYC/AML obligations. This is not legal advice.
Your data responsibilities
Self-hosting gives you control over application data and access. Ecommerce records, server logs and public blockchain data can still exist. Review collection, retention and access with your chosen integration.
12 / FAQ
The details worth knowing before you choose.
What does WebCare360 install?
We deploy and configure BTCPay Server on VPS or dedicated infrastructure selected for your needs, connect the agreed store integration and perform initial payment-flow testing before handoff.
What server do I need?
Sizing depends on store volume, number of stores, blockchain/node requirements, integrations and growth. We review VPS and dedicated options; there is no single specification for every deployment.
Does WebCare360 hold my funds or need my private keys?
The standard setup connects a merchant-controlled wallet and does not require WebCare360 to request or retain your recovery seed, private keys or signing secrets. WebCare360 provides infrastructure and setup, rather than acting as the payment intermediary. Other wallet architectures require separate agreement.
Which payment methods and store integrations can I use?
Bitcoin on-chain is a core platform capability. Lightning requires its own configuration and operating model. The platform documents WooCommerce, Drupal Commerce, Magento and PrestaShop integrations and APIs. Exact methods, versions and deployment scope are reviewed before setup; additional assets and plugins are not automatically included.
What costs remain?
The underlying gateway software does not impose a processing percentage. Infrastructure, WebCare360 setup and integration, payment network fees and any separately agreed services or third-party components remain separate.
Who maintains the gateway and handles backups?
After handoff, ongoing gateway software, store and wallet operation remain customer responsibilities unless separately agreed. Backup coverage depends on your infrastructure/service arrangement. A server backup does not replace merchant wallet recovery material.
How long does deployment take?
Timing depends on infrastructure, wallet/payment methods and integration scope. Agree the deployment and testing window after the requirements have been reviewed.
YOUR PAYMENT INFRASTRUCTURE
Plan your payment
gateway setup.
Tell us about your store, payment methods and infrastructure requirements. We’ll scope the deployment, integration and handoff.