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

# Payment Configuration

> Set up Stripe, Xendit, PayMongo, AFS Gateway and BENEFIT configurations for 9Pic Checkout (Business plan).

> [!WARNING]
>
> Payment Configuration is a **Business plan** feature, and only **team admins** can manage it. On **Trial** it opens in **test mode**: you can use the 9Pic test payment account or add your own Stripe test key (it starts with `sk_test_` or `rk_test_`), and buyers aren't charged. On Pay As You Go and Pro, the sidebar item is muted and explains that it's available on the Business plan. Opening the page shows the same notice with an **Upgrade to Business** button. Payment settings saved on an earlier plan are kept.

> [!NOTE]
>
> **Moving from Trial to Business:** a Stripe test key you saved on Trial is removed when your organisation starts taking live payments. The gateway shows **New key needed**, and events using it take no payments until you select **Edit**, enter the gateway's key and save. Pay As You Go and Pro keep the Trial key.

## Overview

Payment Configuration is where you set up the payment gateways your organisation uses, then map them to events. It powers [9Pic Checkout](https://docs.9pic.ai/products/checkout/overview.md): you create a gateway here once, then assign it to individual events.

Open it from **Payment Config** in the dashboard sidebar (or the **Payment Config** card on the dashboard home).

![Payment Configuration page showing the Payment Gateway Configurations empty state and Event Payment Gateway Status section](https://assets.9pic.ai/docs/dashboard-guide/payment-config/payment-configuration-overview.webp)

Payment Configuration

## Gateway Configurations

The first section lists your gateway configurations and lets you add or edit them.

**1. Create a gateway config**

Add a **Stripe**, **Xendit**, **PayMongo**, **AFS Gateway** or **BENEFIT** configuration with the credentials for that account.

**2. Edit or update**

Open any configuration to update its credentials or details.

**3. Set what buyers see (optional)**

In **Edit**, **What buyers see** holds a **Label buyers see** (up to 60 characters) and a **Note** (up to 120 characters). Buyers see them when an event offers more than one way to pay; each event can change them in its [Checkout configuration](https://docs.9pic.ai/products/checkout/configuration.md). Saving them doesn't ask for your credentials again.

> [!NOTE]
>
> We give clear, gateway-specific instructions during setup. Keep API keys and secrets safe — treat them like passwords and never share them outside your admin team.

## Key Check

When you save a **Stripe**, **Xendit**, **PayMongo** or **AFS Gateway** key, 9Pic checks it with the gateway straight away. The check only reads from your account, so nothing is created and nobody is charged. It runs when you add a gateway, and when you save new credentials (or a new Account ID or Merchant ID) in **Edit**. Renaming a gateway doesn't run it.

> [!NOTE]
>
> The check is for your information only. The gateway is saved whatever the result, and the check never stops you assigning the gateway to an event or buyers paying.

The message after you save tells you the result, for example "Stripe accepted the key." The **Secrets** column in the gateway list keeps it:

| Secrets shows | What it means | What to do |
| - | - | - |
| **Key accepted** | The gateway accepted the key. **Checked** and the date appear under it. | Nothing. Still run a test payment before a live event. |
| **Key not accepted** | The gateway refused the key or credentials. Buyers can't pay through this gateway yet. | Copy the current key or credentials from your gateway account. Select **Edit** on the gateway, enter them and save. 9Pic checks again when you save. |
| **Missing permissions** | The key isn't allowed to read what Checkout needs. Buyers may not be able to pay. | Fix the key's permissions in your gateway account (and any IP allowlist), then select **Check key**. For Stripe, see [Stripe Key Setup](https://docs.9pic.ai/account/payment-gateways/stripe-restricted-key.md). |
| **Configured**, with **Couldn't check the key** | 9Pic couldn't reach the gateway to check. | Select **Check key** to try again. |
| **Configured** | The credentials are saved but haven't been checked. BENEFIT always shows this. | For BENEFIT, run a test payment. For other gateways, select **Check key**. |

When a key isn't accepted or is missing permissions, a note above the list names the gateway and explains the fix. For Stripe, it names the rows the key can't use, such as **Checkout Sessions, Invoices**. If a buyer's payment has already failed on that gateway, you see the **Key rejected**, **Payments blocked** or **Payment checks blocked** warning instead. Fix that one first.

### Check Key

**Check key** sits next to **Edit** in the **Actions** column for Stripe, Xendit, PayMongo and AFS Gateway configurations that have saved credentials. Select it after you fix a key's permissions, or any time you want to confirm the key still works. The result appears in a message and in the **Secrets** column. Checking doesn't change **Last Updated**, and it doesn't clear a **Key rejected**, **Payments blocked** or **Invoices blocked** warning. Those clear after the next successful payment or invoice, or when you save a new key.

### What 9Pic Checks

| Gateway | What 9Pic checks |
| - | - |
| **Stripe** | Stripe accepts the key, and the key can read **Checkout Sessions**, **Customers**, **Payment Intents** and **Invoices**. |
| **Xendit** | Xendit accepts the key, and the key can list your payment links. |
| **PayMongo** | PayMongo accepts the key, and the key can read your account's payment methods. |
| **AFS Gateway** | AFS accepts the Merchant ID and API password. 9Pic looks up an order that doesn't exist, and AFS only answers "no such order" when it accepts the credentials. |

Stripe write access can't be checked without creating a payment, so your first test payment confirms it. BENEFIT, **No gateway** and the 9Pic test payment account aren't checked. BENEFIT can only tell whether its details work when a buyer pays, so run a test payment.

## Stripe Restricted Key

For Stripe, create a restricted key before you add the gateway in 9Pic. The key should grant only the Stripe permissions needed for Checkout, payment checks, invoices and, if you use Stripe tax, reading your tax rates and Stripe Tax settings.

> [card] [Stripe Key Setup](https://docs.9pic.ai/account/payment-gateways/stripe-restricted-key.md)
>
> Follow the end-to-end Stripe restricted key setup, including screenshots and the permission checklist.

## AFS Gateway

AFS Gateway supports 9Pic Checkout through Mastercard Hosted Checkout. Add the AFS **Merchant ID** and **API password** in Payment Configuration, then assign that configuration to an event. A Merchant ID beginning with `TEST` uses the simulator; use the separate live Merchant ID for real payments.

> [card] [AFS Gateway Setup](https://docs.9pic.ai/account/payment-gateways/afs-gateway.md)
>
> Follow the AFS credential, test, live-payment, and event-assignment steps.

## BENEFIT

BENEFIT lets buyers in Bahrain pay with BENEFIT debit cards, in **BHD** only. Add the **Tranportal ID**, **Tranportal password** and **Terminal resource key** from your BENEFIT merchant portal. **Test environment** is on by default; turn it off only with the live Tranportal details BENEFIT gives you at go-live. In **Edit**, leaving the password or resource key empty keeps the saved one. You can offer BENEFIT next to AFS Gateway on the same event so buyers choose debit or credit cards.

> [card] [BENEFIT Setup](https://docs.9pic.ai/account/payment-gateways/benefit-gateway.md)
>
> Follow the BENEFIT credential, test, live-payment, and event-assignment steps.

## PayMongo

PayMongo supports 9Pic Checkout for **PHP** photo sales in the Philippines. Add the PayMongo **secret key** in Payment Configuration, then assign that configuration to an event. Use a `sk_test_` key for setup checks and a `sk_live_` key for public checkout.

> [card] [PayMongo Setup](https://docs.9pic.ai/account/payment-gateways/paymongo.md)
>
> Follow the PayMongo secret-key, test, live-payment, and event-assignment steps.

## Xendit

Xendit supports 9Pic Checkout for **IDR, PHP, MYR, THB, and VND** photo sales. Add the Xendit **secret key** in Payment Configuration, then assign that configuration to an event. Xendit does not offer a Pass on fees option, and 9Pic does not automatically enforce which key mode (development or production) you use.

> [card] [Xendit Setup](https://docs.9pic.ai/account/payment-gateways/xendit.md)
>
> Follow the Xendit secret-key, test, live-payment, and event-assignment steps.

## Tax Configuration

The **Tax Configuration** tab has a section menu on the left with two sections:

| Section | Used for | What you set |
| - | - | - |
| **Regular tax** | The tax profile on 9Pic receipts for gateways other than Stripe | Tax name, tax ID and percentage, saved with **Save tax profile**. Each event turns **Show tax on receipts** on in **Payments → Receipts and tax** and chooses whether package prices include it |
| **Stripe gateway tax** | Purchases paid through each of your Stripe gateways | **No tax**, **A tax rate from your Stripe account** or **Stripe Tax (automatic)**, once per gateway, saved with **Save Stripe gateway tax**. Each event chooses **Package prices** (include tax or add it at checkout) in **Payments → Stripe purchases** |

**Regular tax** opens first (link: `/payment-configuration/tax`). The **Stripe gateway tax** section (link: `/payment-configuration/tax?section=stripe`) lists each Stripe gateway of your own; if you have none yet, it asks you to add one in **Gateway Configurations**. It needs **Sales tax settings** on your plan; without them it shows the plan lock, unless a gateway still has a saved tax, which you can turn off. Saving is refused while an event using the gateway needs a kind of rate your Stripe account lacks; the error names those events. See [Stripe Invoice Setup](https://docs.9pic.ai/account/payment-gateways/stripe-invoices.md#stripe-tax) for the full steps, the inclusive and exclusive rate rules, and a worked AUD example.

![Tax Configuration with the 9Pic receipt and Stripe tax tabs, Stripe tax open for a Stripe gateway with A tax rate from your Stripe account chosen, Tax GST 10% Australia, rates found for Prices include tax and Tax added at checkout](https://assets.9pic.ai/docs/dashboard-guide/payment-config/stripe-tax-tab.webp?v=20261105c)

The Stripe gateway tax section of Tax Configuration.

## Event Mapping

The second section maps events to a gateway configuration, so each event's checkout routes payments to the right account. This is the organisation-level counterpart to the per-event gateway assignment you do on the [Checkout Configuration](https://docs.9pic.ai/products/checkout/configuration.md) tab.

## Who Can Access It

| Requirement | Detail |
| - | - |
| **Plan** | Business or Enterprise (test mode only on Trial) |
| **Role** | Team admin |
| **Organisation** | One must be selected in the top bar |

If you're on Business or Enterprise but see an "Access Denied" notice, your account isn't a team admin — ask an admin on your [Team](https://docs.9pic.ai/account/team.md) to grant access.

## Next Steps

> [card] [9Pic Checkout](https://docs.9pic.ai/products/checkout/overview.md)
>
> Sell photos, videos, and certificates per event.

> [card] [Checkout Configuration](https://docs.9pic.ai/products/checkout/configuration.md)
>
> Assign one of these gateways to an event.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.