WeeConnectPay Developer Documentation
Public integrator documentation for the WeeConnectPay API — the Clover payments
bridge for e-commerce platforms. Agent-readable index at
/llms.txt.
- Currency Preflight Guide — Read the merchant.currency block from get-caller-identity before mounting the Clover payment iframe, and block a doomed checkout up front on a known cart-currency mismatch.
- Device Authorization Guide (RFC 8628) — Obtain WeeConnectPay OAuth2 client credentials through the RFC 8628 device flow — the recommended plugin onboarding path, with endpoints, polling rules, and worked examples.
- Device Authorization vs. Legacy OAuth Flow — Side-by-side comparison of the RFC 8628 device flow and the legacy OAuth redirect chain for plugin onboarding, from the provider, plugin-developer, and merchant perspectives.
- Integration Architecture Guide — What a WeeConnectPay access token represents, how Clover merchant/app/employee entities relate, and how to design integrations that survive real-world disruptions.
- OAuth2 Integration Guide — Authenticate with the WeeConnectPay API using OAuth2 client credentials — environments, token requests, JWT lifetime, and error handling for third-party integrations.