> ## Documentation Index > Fetch the complete documentation index at: https://docs.shoply.gg/llms.txt > Use this file to discover all available pages before exploring further. # Custom payment methods > Take payments Shoply has no integration for, such as a bank transfer or your own pay page, and approve each order yourself A custom payment method is a way to be paid that Shoply does not connect to: a bank transfer, a payment app, a page of your own. The buyer pays you outside Shoply, tells you they have, and the order waits for you. You check your own account, then approve the order to deliver it, or reject it. Shoply never sees this money and cannot tell whether it arrived. Your look at your own account is the only check. ## Adding one Open **Settings**, then **Payment Options**, then **Payment Methods**. **Custom Payment Methods** is under the methods you have connected. Press **Add Method**. | | | | - | - | | **What the Buyer Is Shown** | **Instructions**, words the buyer reads on the checkout, such as your bank details. Or **Your Own Page**, an address the buyer is sent to, in a new tab, to pay on. | | **Name** | What buyers see it called, up to 60 characters. | | **Description** | One line under the name at checkout, up to 160 characters. | | **Instructions** | How to pay, up to 300 characters. Markdown works: bold, lists and links. | | **Address** | For your own page: an address that starts with `https://`, up to 1,000 characters. | | **Icon** | Shown beside the name at checkout. Without one, a banknote is. | | **Ask for Proof** | When the buyer says they have paid, they send the payment's reference or a proof of payment. At least one of the two. | | **Require Proof of Payment** | Under **Ask for Proof**: the buyer cannot say they have paid without a picture of the payment. The checkout marks the box with a red asterisk. | A store can have up to 10. Each one is a row of the list of your payment methods, at the top of **Payment Methods**, marked **Custom**: a new one goes last. Its switch takes it off the checkout without deleting it, and its menu edits or deletes it. Drag a row by its grip to put it anywhere in the list, above your connected methods too: the checkout offers them in that order. ### Filled in for each order Write any of these in the instructions or the address, and the buyer sees it filled in for their order: | | | | - | - | | `{order}` | The order's ID, whole, as its pages write it, such as `a2855h0p1y4-71329ed4d95-1000427` | | `{amount}` | What the payment is for | | `{currency}` | Its currency | | `{email}` | The buyer's email | | `{store}` | Your store's name | So `https://pay.example.com/?order={order}&amount={amount}` sends a buyer to `https://pay.example.com/?order=e09dd7db&amount=24.99`. Anything else in braces is refused when you save. ## What the buyer does Custom methods are listed at checkout where you put them among your other methods. 1. The buyer picks it and presses **Pay**. They read your instructions, or their tab opens your page. 2. They pay you, the way you said. 3. Back on the checkout, they fill in the **Payment Reference** and add a **Proof of Payment** where you asked for them, and press **I Have Paid**. All of it is on one page. A proof of payment is a PNG, JPEG or WebP picture of up to 5 MB. It is kept privately: only you see it, on the order's page. Once they have said they paid, the checkout says it is being checked, and the order cannot be paid another way while you look. It is not cancelled as an [unpaid order](/guides/payment-methods.md#unpaid-orders) while it waits. What the buyer was told is fixed when they press **Pay**. A change you make to the method afterwards, or switching **Require Proof of Payment** on, applies to the next buyer. ## Approving or rejecting You are told when a buyer says they have paid: * **Email Me When a Payment Needs Checking**, in **Notifications**, is on for every store. With no address of your own there, it goes to your account's email. * **Payments to Check**, under **On Discord**, posts it to your Discord channel. It started on for stores that already used Discord; switch it on for yours if not. The order's page has a **Payment Outside Shoply** card: the method, the amount, the reference, when it was sent, and the proof of payment, which opens whole in a new tab. * **Approve and Deliver** completes the order as a paid one: the buyer is sent what they bought. If the order cannot be delivered, out of stock say, it says why and goes on waiting. * **Reject** cancels the order and releases any coupon it used. The buyer is not emailed. You can still [mark it as paid](/guides/orders.md#mark-as-paid) later. ## Your server A [webhook](/guides/webhooks.md), `order.payment_submitted`, is sent with the order when a buyer says they have paid. Approving it sends `order.paid` and the order's other events, as any payment does, and rejecting it sends `order.cancelled`. With an [API key](/guides/api-keys.md), your server can approve or reject a payment and download its proof of payment, which needs **Deliver Orders**, and add, change, sort, switch and delete the methods themselves, which needs **Change Payment Methods**. A script that watches your own bank account could approve each payment it sees arrive. Shoply still never sees the money, and approving delivers the order. See [Approve a payment to check](/api-reference/orders/approve-a-payment-to-check.md) and [Custom payment methods](/api-reference/custom-payment-methods/list-custom-payment-methods.md) in the API reference. ## Refunds Shoply cannot send this money back. **Refund Order** credits the buyer's [store balance](/guides/customers-and-balance.md), or records a refund you made yourself. ## What they do not do * They are not offered on an [invoice or a payment link](/guides/orders.md#invoices). * A product's fee for a payment method is set per connected provider, so a custom method carries none. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.