# Integration Options

Building with an AI agent? Start at https://docs.payme.io/agents.md

## Related

- [Start Here](/payments/getting-started/start-here)
- [Quickstart](/payments/getting-started/quickstart)
- [Create a sale (hosted payment page)](/payments/hosted-payment-page/post-generate-sale)

Building with an AI agent? Start with the [AI Toolkit](/agents).

There are three ways to take a payment. They differ in who renders the card form and how much of PCI DSS falls on you.

| Option | How it works | Choose it when | Trade-offs |
|---|---|---|---|
| [Hosted Payment Page](/payments/hosted-payment-page/post-generate-sale) | Your server calls `generate-sale`; the buyer pays on PayMe's page (`sale_url`) in an iframe or a redirect. | You want the fastest integration, every payment method on one page (`multi`), and PayMe to carry PCI DSS. | Limited control over the page design. |
| [Hosted Fields (JSAPI)](/accepting-payments/checkout-and-in-person/hosted-fields-jsapi-guide) | PayMe's card inputs (iframes) sit inside your own form; the browser gets a token and your server charges it with `generate-sale` and `buyer_key`. | You want your own checkout design without card data touching your servers. | More front-end work; your Content Security Policy must allow `cdn.payme.io` and `hf.payme.io`. |
| [Direct API](/payments/direct-api) | Your server sends card details to `pay-sale`. | You are PCI DSS level 1 compliant and need full control. | You carry PCI DSS compliance; PayMe must enable the API for you. |