ChargeAfter

The ChargeAfter Developer Hub

Welcome to the ChargeAfter developer hub. You'll find comprehensive guides and documentation to help you start working with ChargeAfter as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    

What is ChargeAfter?

ChargeAfter is a market-leading platform that connects merchants and lenders to offer consumers personalized Point of Sale Financing options at checkout from multiple lenders, across all financial products and credit ratings, through all channels: online, in-store and call center.

We offer retailers the ability to use financing to drive business and increase their AOV, revenue and margins. The power of the platforms allows us to provide offers to 85% of the customers, compared to 25-50% approval that is provided by any single lender solution. We allow the merchant to provide highly customizable global solution with with a very simple, low friction and minimal integration solution.

📘

These pages are dedicated resources for ChargeAfter's merchant partners and developers. If you’re a consumer, please visit our web site.

How does it work?

ChargeAfter platform provides 3 integration channels or merchants. The merchants can chose the most appropriate integration approach based on the scale of sales, technology capabilities of the team and functional requirements.

  1. Integrate via the eCommerce Plugins available on the most popular eCommerce platforms (Magento, Shopify, BigCommerce, etc.). See the Platforms section for more details about this approach.

  2. Integrate via the JavaScript SDK. This is the preferred integration approach for stores that don't work with any of the supported eCommerce platforms.

  3. Integrate programmatically via the RESTfull API exposed by ChargeAfter. This approach enables the merchant to build it's own checkout experience and UI by leveraging ChargeAfter core capabilities.

Updated 10 months ago



Overview


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.