Payment Methods API
Every project configures one or more payment providers so subscribers can buy plans.
Every project configures one or more payment providers so subscribers can buy plans. These endpoints let you read which providers a project has connected and in what mode, switch each one on or off, push the plan catalogue to its gateway again, and remove one. Entering or rotating credentials remains dashboard-only, because each provider needs its own OAuth or secret-entry flow that a generic REST layer cannot safely reproduce.
Endpoints
GET
/v1/projects/{project}/payment-methodsList a project's payment methodsGET/v1/projects/{project}/payment-methods/{method}Get a payment methodDELETE/v1/projects/{project}/payment-methods/{method}Delete a payment methodPOST/v1/projects/{project}/payment-methods/{method}/activateActivate a payment methodPOST/v1/projects/{project}/payment-methods/{method}/deactivateDeactivate a payment methodPOST/v1/projects/{project}/payment-methods/{method}/syncSync a payment method's plansRelated
Payment MethodsStripe, PayPal, Skrill, CoinPayments, Paystack, Razorpay, CeyPay, native payments and access codes compared: regions, currencies, recurring, crypto.project.* eventsConnecting a gateway raises no event, so the first thing an endpoint hears about a new method is its first update or its deletion; credentials never appear in a payload, and when keys are rotated from the dashboard changes.config.keys names which keys changed and nothing else.
How is this guide?
Last updated on