---
id: home
title: Start here
summary: Three 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

Three ways to take a payment. Most integrations use more than one, and they are layers rather than
alternatives: a checkout on your page almost always has a server behind it.

## The checkout on your page

One script tag, or the npm package, or the React component. The shopper pays without leaving your site, and
your page is told what happened.

Start at the [Quickstart](/quickstart) and pick your platform.

## The API from your server

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

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

## The hosted payment page

No code at all. You get a link, the shopper pays on a page we host, and you read the outcome the same way.

Start at [The hosted page](/js/hosted-page).

## If you are not sure

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.

If you are using an AI coding assistant, point it at [/llms.txt](/llms.txt) — every page is also served as
markdown, and the error codes, test cards and policy requirements are published as data it can read directly.