Platform Architecture
Invisible infrastructure.
Powerful results.
WGC sits directly between your software and the banking system, allowing you to build the ideal giving experience while we handle the complexity of money movement.
✝
Layer 01
Partner Application
The Protocol
WGC Payments
Gateway API
Gateway API
Layer 03
Financial Core Rails
Architecture Stack
Three-Layer Platform
The clear separation of concerns in our unified platform infrastructure.
Layer 1 — Your Platform
Partner Software
Your ChMS, giving app, or ministry suite. WGC integrates through a clean REST API — completely white-labeled under your brand.
Layer 2 — WGC Infrastructure
Waypoint Gateway Collective
API management, partner authentication, fee calculation, merchant routing, reporting, recurring billing, and webhook delivery.
Layer 3 — Banking Rail
WGC Core Processing
PCI Level 1 certified card processing and ACH network. Settlement, compliance, and bank-grade security — fully managed.
What Happens When Someone Gives
A donation processed in real time — from tap to treasury.
1
Donor initiates a gift
A donor taps "Give" inside your app. Your software calls the WGC API with the amount, fund, and donor payment method.
2
WGC authenticates the partner request
The request is validated against your Partner API key. Merchant routing and fee calculations happen in milliseconds.
3
Network processes the payment
WGC sends the tokenized transaction to the secure core. Card or ACH is authorized through the banking rail with full PCI compliance.
4
WGC fires your webhook
Your application receives a real-time event notification — payment.succeeded, payment.failed — so your UI updates instantly.
5
Funds settle to the church
Net proceeds move to the merchant's verified bank account. Settlement windows vary by rail — ACH: 1-2 days, Card: 2-3 days.
Ready to integrate?
Join software partners building Kingdom-aligned giving experiences with WGC.
Contact Sales