← Back to Features
CONNECTION ENGINE
The Service Provider Gateway
Bills connect to income, not to cards. Zero failed payments. Zero expired card numbers. Zero bounced direct debits.
The death of the bounced payment
Traditional direct debits pull from a bank account and fail when it's empty. tPay365 inverts this — providers connect directly to the income stream. Payments execute from the vault, where money is always waiting.
1
tPay_ID (No-Code)
Provider shares their tPay_ID. User links it in the app. Done. No API integration required. Works for any provider in seconds.
2
API Integration
Provider embeds a "Connect with tPay365" button. OAuth 2.0 flow. Automatic recurring payments with real-time reconciliation.
tPay365
Engine
Engine
Energy
£85/mo
Streaming
£15.99/mo
Telecoms
£35/mo
Insurance
£45/mo
Fitness
£29.99/mo
Every payment sourced from ring-fenced vaults. The provider's money is always there.
Technical Specification
Connection methods: 1. tPay_ID (no-code) — share ID, user links 2. API — OAuth 2.0 "Connect with tPay365" flow Payment source: Bills Vault (ring-fenced from spending) Execution: Due date scheduler or provider webhook Settlement: T+0 for vault → provider Retry: Automatic on transient failure (max 3) Reconciliation: Real-time webhook to provider
provider-connect-button.png"Connect with tPay365" button embedded on provider checkout page
provider-dashboard.pngProvider dashboard showing connected subscribers and payment status
API Endpoints
GET
/api/v1/employer/employeesList connected employeesGET
/api/v1/employer/wellnessWellness metricsPOST
/api/v1/employer/reportsGenerate reports