Skip to content
DevelopersReference

Payments

Storefront payments and processor webhooks.

1 min readUpdated View as Markdown

Generated from the gateway's route table. Base URL https://papi.dashfordevs.com. Send your key in X-API-Key.

Method Path Key Status Notes
GET /api/storefront/auth/invoices Public or secret key Live (payments)*
GET /api/storefront/auth/stripe-payment-methods Public or secret key Live (payments)*
POST /api/storefront/auth/billing-portal Public or secret key Live (payments)*
GET /api/storefront/payment/processor Public or secret key Live (payments)*
GET /api/storefront/payment/client-config Public or secret key Live (payments)*
POST /api/storefront/payment/charge Public or secret key Live (payments)*
POST /api/storefront/payment/authorize Public or secret key Live (payments)*
POST /api/storefront/payment/capture Public or secret key Live (payments)*
POST /api/storefront/payment/void Public or secret key Live (payments)*
GET, POST /api/customer/payment-methods/ Public or secret key Live (payments)*
DELETE /api/customer/payment-methods/{profile_id}/delete/ Public or secret key Live (payments)*
POST /api/customer/payment-methods/{profile_id}/set-default/ Public or secret key Live (payments)*
POST /api/webhooks/authorize/recurring/ No key Live (payments)*
POST /api/webhooks/quickbooks/ No key Live (payments)*

* Customer data and payments routes work for every organization except HIPAA organizations, which get 503 not_available_yet (with "available": false) until that organization's HIPAA path is complete. Not built yet routes answer 501 not_implemented.

Keep reading

Something wrong or missing on this page? Email support@dashfordevs.com.