> ## Documentation Index
> Fetch the complete documentation index at: https://docs.komerza.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Custom Payment Methods

> Accept bank transfers, Zelle, manual crypto or any other payment you settle yourself

Custom payment methods let you accept anything Komerza doesn't integrate with - bank transfer, Zelle, Wise, a manual crypto address, cash on collection. You define the method, the customer follows your instructions and submits proof of payment, and you approve or reject the order yourself.

They are configured in the dashboard under **Online Store → Settings → Payment Methods**.

<Note>
  Custom methods are **manually settled**. Komerza never sees the money, cannot
  confirm that payment arrived, and cannot refund it. Everything depends on you
  verifying payment before you approve.
</Note>

## The two types

<CardGroup cols={2}>
  <Card title="Instructions" icon="list-ol">
    The customer is shown text you write - bank details, a wallet address, a
    reference to include - and pays outside Komerza.
  </Card>

  <Card title="Redirect" icon="arrow-up-right-from-square">
    The customer is sent to a URL you specify to complete payment, then returns
    to confirm.
  </Card>
</CardGroup>

Each method has a **name**, an **icon** (PNG, JPG or WebP up to 2 MB) and a **sort order** controlling where it appears in the checkout list.

## How the customer experience works

<Steps>
  <Step title="The customer selects your method at checkout">
    It appears alongside your other gateways, using the name and icon you set.
  </Step>

  <Step title="They follow your instructions or your redirect">
    Payment happens entirely outside Komerza.
  </Step>

  <Step title="They click &#x22;I have paid&#x22; and submit proof">
    Proof is a transaction reference, a screenshot (up to 5 MB), or both.
  </Step>

  <Step title="The order sits in Pending">
    It shows as **Awaiting seller review** with a Proof of Payment card on the
    order page.
  </Step>
</Steps>

## Approving or rejecting

Open the order under **Home → Orders** and review the Proof of Payment card:

* **Approve & Deliver** - the order runs the normal delivery flow and becomes **Delivered**.
* **Reject** - the order becomes **Cancelled**.

<Warning>
  Verify the money actually arrived in your account before approving. Approval
  triggers real delivery - stock is consumed, license keys are issued, dynamic
  delivery webhooks fire and the customer is emailed. A screenshot is not proof
  of settlement.
</Warning>

<Tip>
  Turn on the **Order Pending** notification under **Store Settings →
  Notifications** so a submitted proof doesn't sit unnoticed. Slow approvals are
  the most common complaint about manual methods.
</Tip>

## Refunds

Orders paid with a custom payment method can only be refunded to **customer balance**, because there is no gateway to reverse the charge through. Refunding the actual money is something you do yourself, through whatever channel the customer paid with.

Balance refunds require your store's customer balance feature to be enabled under **Settings → Payment Options** - otherwise you will see "Customer balance is not enabled for this store."

See [Managing Orders](/guides/orders#refunds) for the full refund flow.

## Fees, minimums and labels

Custom methods sit alongside every other gateway in **Settings → Payment Options**, where you can set:

* A per-gateway **percentage and fixed fee** passed on to the customer
* A **minimum order** amount (never below the system floor of 0.50 in your store currency for non-crypto methods)
* A **checkout label** that renames the method at checkout

## When to use a custom method - and when not to

Custom methods are the right tool for payment rails Komerza doesn't support, low volumes, or high-trust B2B sales where you already know the buyer. They scale poorly: every order needs a human decision, and there is no automatic matching of incoming payments.

If you need automated crypto acceptance rather than a manual wallet address, use a supported processor instead - see [Self-Custody](/guides/self-custody-setup), [NOWPayments](/guides/nowpayments-setup) or [Heleket](/guides/heleket-setup). For automated card payments, see [Supported Payment Methods](/guides/payment-methods).

## Next steps

<CardGroup cols={2}>
  <Card title="Supported Payment Methods" icon="credit-card" href="/guides/payment-methods">
    Every integrated gateway and cryptocurrency.
  </Card>

  <Card title="Managing Orders" icon="receipt" href="/guides/orders">
    Approve, deliver, refund and export orders.
  </Card>

  <Card title="Payment Method Reference" icon="book" href="/api-reference/payment-methods">
    Payment method values used by the API.
  </Card>

  <Card title="Order Status Reference" icon="list-check" href="/api-reference/payment-status">
    What Pending, Delivered and Cancelled mean.
  </Card>
</CardGroup>