> For the complete documentation index, see [llms.txt](https://hollow-peak.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hollow-peak.gitbook.io/docs/payments/payment-architecture.md).

# Payment Architecture

Methods versus providers, and why the distinction matters.

Hollow Peak separates two things most systems blur together.

## Methods and providers

A **payment method** is what the customer chooses — card, PayPal, bank transfer.

A **payment provider** is the company that processes it — Stripe, PayPal, or you personally in the case of a bank transfer.

The two are connected by **routing**. You decide which provider handles which method.

```
Customer chooses      Routed to           Processed by
─────────────────      ─────────           ────────────
Card             →    Stripe         →    Stripe's hosted page
PayPal           →    PayPal         →    PayPal
Bank transfer    →    Manual         →    Your bank account
```

If you later switch cards from Stripe to Safepay, customers see the same “Card” option. Only the routing changes.

## Apple Pay and Google Pay

{% hint style="warning" %}
Apple Pay and Google Pay are **not separate gateways** in Hollow Peak. They are wallet methods presented **by Stripe** inside Stripe's own checkout.

They require Stripe, HTTPS, and domain registration in your Stripe dashboard. They cannot be enabled independently of Stripe.
{% endhint %}

The checkout refuses a wallet method over plain HTTP, because the wallet will not appear there anyway.

## The five providers

| Provider                 | Processes                        | Availability                      |
| ------------------------ | -------------------------------- | --------------------------------- |
| **Stripe**               | Cards, Apple Pay, Google Pay     | Wherever Stripe accepts merchants |
| **PayPal**               | PayPal balance, cards via PayPal | Wherever PayPal accepts merchants |
| **Manual bank transfer** | Offline transfers                | Anywhere                          |

{% hint style="info" %}
**Availability is the provider's decision, not Hollow Peak's.** No provider works everywhere. Check that your country and business type are supported before building a shop around one.
{% endhint %}

## When a method is offered

A method appears at checkout only when **all** of these are true:

1. The Payments module is enabled
2. The provider is switched on
3. The provider has credentials
4. The provider supports that method
5. The provider supports your currency
6. For wallets, the connection is HTTPS
7. For bank transfer, at least one bank account is configured

If a method is missing, one of these is the reason. The Payments settings screen states which.

## What never happens

**Card details never reach the application.** Every card payment happens on the provider's own page, or inside their iframe. Hollow Peak never receives a card number, expiry or security code.

**Prices are never taken from the browser.** The amount is recalculated on the server from your catalogue at checkout. A modified price in a form submission changes nothing.

**A return URL is never proof of payment.** Coming back from a provider triggers a server-to-server confirmation. The browser's claim is not evidence.

**An unverified webhook is never believed.** Signatures are checked before anything changes, and there is no setting that relaxes this.

## Order of setup

1. **Store → Settings** — set your currency first
2. **Payments → Settings** — enable a provider and enter sandbox credentials
3. Press **Test** and confirm it succeeds
4. Register the webhook with the provider
5. Place a complete test order
6. Switch to live credentials and test again with a small real payment


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hollow-peak.gitbook.io/docs/payments/payment-architecture.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
