---
id: home
title: Start here
summary: Four ways to take a payment with ripper, and where each one begins.
faces: ["public", "agent"]
section: shared
group: Get started
slug: ""
order: 1
next: ["how-it-works"]
---
# ripper docs

## I just want to take a payment

No code. Every merchant has a payment page we host: you get a link, the shopper pays on it, and you read the
outcome the same way as everyone else. If you have no site to change, or you do not want to change it, start
and finish here.

[Use a payment link](/js/hosted-page)

## Building with an AI tool

For sites built in Lovable, Replit, Base44, Netlify and the like, where the tool writes the code.

[What this route will be](/ai-builders)

## The checkout on your page

The shopper pays without leaving your site, and your page is told what happened. A script tag, the npm
package, or the React component — that choice is yours to make inside this route, and the Quickstart asks it
first.

[Start at the Quickstart](/quickstart)

## The API from your server

Create a session, read a payment, receive a webhook. This is where your business decides an order is paid, and
it is the half that should never be trusted to a browser.

[Start at the API reference](/api/reference)

## Not sure which

Read [How ripper checkout works](/how-it-works) first. It is short, it names every piece once, and the rest of
these docs are easier afterwards. Most integrations end up using more than one of these routes: a checkout on
your page almost always has a server behind it.