> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/payments/magpie-podcredits.md).

# Magpie PodCredits

{% hint style="success" %}
**This article is for international Clubs where Stripe is not available.**
{% endhint %}

### Overview

PodPlay processes Customer payments through Stripe. Stripe does not operate in the Philippines, so Clubs there run on Credits instead of direct card charges. Customers load Credits into a Wallet through PodCredits, a local Payment Service Provider (PSP) connected to Magpie, and every Reservation is paid from that Credit balance.

Before Customers can load Credits or book, the Club signs up for its own PodCredits account and gets it approved. The Club's Owner then connects that account to the Club's Environment, with help from the PodPlay onboarding manager if needed. PodPlay turns on local payments and runs a test booking.

{% hint style="warning" %}
**The current PodCredits integration supports Philippine pesos (PHP) only.** If your Club operates in another country where Stripe is not available, contact your PodPlay onboarding manager before you start setup.
{% endhint %}

### What changes when your Club runs on Credits

| Area                  | Clubs with Stripe                               | Clubs on PodCredits                                                                         |
| --------------------- | ----------------------------------------------- | ------------------------------------------------------------------------------------------- |
| How Customers pay     | Card on file, charged per Reservation           | Credits loaded into the Wallet, then spent on Reservations                                  |
| When payment is taken | The system places a hold on the card by default | Credits are subtracted from the Profile immediately at booking                              |
| Deposits              | Depends on Club settings                        | Not supported. The full booking amount comes out of Credits                                 |
| Supported purchases   | Reservations, Memberships, shop, and more       | Court Reservations and Coach Lessons only. Memberships and shop purchases are not supported |
| Opting out of Credits | Not applicable                                  | Not possible. The Environment must run on Credits                                           |

Every Customer must create a free Profile in the Web App or App before booking. There is no guest checkout.

### Set up PodCredits for your Club

PodPlay cannot create the PodCredits account for you. The Club completes steps 1 through 4 with the PodCredits team, and PodPlay completes steps 5 and 6.

1. Get an introduction to the PodCredits team from your PodPlay onboarding manager. The PodCredits team sends you the PodCredits signup link
2. Sign up with a login that belongs only to your Club, create your password, and log in with the verification code sent to your email
3. Submit your identity and business verification, request your payment methods, and add a bank or e-wallet account for settlement. PodCredits reviews and approves your account
4. Connect PodCredits to PodPlay. See Connect PodCredits to PodPlay
5. PodPlay turns on local payment processing in place of Stripe
6. PodPlay runs a test Reservation paid with Credits, then walks your team through the booking experience from the Customer's side

{% hint style="warning" %}
**Do not share one PodCredits login across Clubs.** Each Environment takes exactly one set of credentials and one merchant slug. If you operate more than one Club, each Club needs its own PodCredits account.
{% endhint %}

{% hint style="info" %}
**Plan for approval before your opening date.** Verification requires business documents, and approval takes time on the PodCredits and Magpie side. Allow at least three weeks from the PodCredits introduction to a working connection, and start as early as possible in onboarding so your Club can test bookings before it opens.
{% endhint %}

#### Connect PodCredits to PodPlay

You need the Owner role in the PodPlay Environment for this step. Only the Owner role can open `Company Settings`.

1. In the PodCredits dashboard, open `Checkout`, find `Merchant slug`, and click `Copy`
2. In the PodPlay Dashboard, open `Company Settings`, then the `Integrations` tab
3. In the `PodCredits/MagPie PSP` section, turn on the `PodCredits Integration` toggle. A checkmark means on and an X means off
4. Fill in the fields listed below
5. Click `Save Changes` at the top of the page
6. Check that `Token Status` shows Valid
7. Tell your onboarding manager the token is valid, so PodPlay can finish steps 5 and 6

<figure><img src="https://748075183-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhUuyvUAmLenY3wXHr6EP%2Fuploads%2FYgB44dUvuODwglaL2FaO%2F2602051246-podcredits-config-1a2b3c.png?alt=media&#x26;token=4878ca65-91ba-4b5e-a14a-dd01ec1fcc3a" alt="PodCredits/MagPie PSP section on the Integrations tab"><figcaption></figcaption></figure>

| Field           | What to enter                                                                           |
| --------------- | --------------------------------------------------------------------------------------- |
| `User Email`    | The email address of an admin on your PodCredits account.                               |
| `Merchant Slug` | The merchant slug you copied from `Checkout` in the PodCredits dashboard.               |
| `Password`      | The PodCredits account password. Click `Edit PodCredits Password` to show or change it. |

{% hint style="danger" %}
**Do not send your PodCredits password by email.** Enter it yourself in `Company Settings`, or enter it together with your onboarding manager on a call.
{% endhint %}

#### Token status

`Token Status` sits below the password field and shows whether the PodCredits access token is valid and when it expires.

* **Valid (green):** The token is active and PodCredits can process payments.
* **Invalid or Expired (red):** Payments that rely on PodCredits can fail. Re-enter the password, then click `Save Changes` so PodPlay can get a new token.

Changing the password invalidates the current access token. Save after every password change, then check `Token Status` again.

`Save Changes` saves every section of `Company Settings` at once. `Discard Changes` restores the last saved values. If the settings fail to load, click `Retry`.

#### Testing before setup is complete

You cannot test a Reservation until PodCredits is connected. Adding Credits to a test Customer from the Dashboard does not work around this, because the booking needs the payment connection in place first. Your Club's location and courts also need to be live. Once PodCredits is connected, a Wallet top-up can be tested on its own. You can explore the Web App, the Dashboard, and the booking pages in the meantime.

### What Customers see

#### Loading Credits into the Wallet

1. Sign in to the Web App
2. Open `Account`, then open the `Wallet`
3. Choose the amount to load
4. Scan to pay with QR Ph, or enter card details to complete the payment

The amount is added to the Customer's Credit balance after the payment goes through.

Credits are bought in bulk, not per Reservation. The minimum top-up is PHP 25. A Customer who wants to book only once loads the amount of that Reservation.

{% hint style="info" %}
**Customers load Credits in the Web App.** Customers can spend Credits in the iOS and Android Apps. Ask your onboarding manager whether your Apps also support loading Credits.
{% endhint %}

#### Booking a court

Once a Customer has Credits, they browse available courts and book. The cost of the Reservation comes out of their Credit balance automatically, so there is no separate payment step at booking. When the balance runs low, the Customer loads more Credits in the Wallet.

### Handling cash at the front desk

Wallet top-ups accept QR Ph and card only. Cash is handled at the front desk, and it works two ways. Ask the Customer first which one they want.

#### Option 1: Book one Reservation paid in cash

Use this when a Customer at the Club wants to book and pay on the spot without a Credit balance. Only staff can do this. A Customer cannot do it on their own.

1. Click and drag on the Dashboard to highlight the Customer's preferred time
2. In the side panel, search for the Customer by name
3. Click the blue `Book` button
4. Select `Cash` as the payment method in the pop-up
5. Finalize the Reservation
6. Collect the cash from the Customer

No Credits are used in this flow.

#### Option 2: Load Credits with cash

Use this when a Customer wants to fund a Credit balance with cash, the same way another Customer loads the Wallet by card. Staff need the Manager role or above to add Credits. The Front Desk role cannot add Credits.

1. Collect the cash from the Customer
2. Open the Customer's Profile in the Dashboard
3. Click the pencil icon next to the `Credit` section
4. Select `Add` and enter the amount received
5. Type a reason for the addition. The reason is required
6. Confirm the addition

The amount is now in the Customer's Credit balance, the same as a card top-up.

{% hint style="warning" %}
**PodPlay cannot confirm that cash changed hands.** PodPlay keeps a Credit history record of every addition, and your team should still keep its own record of cash received for both options. Managers should reconcile the cash drawer against system records at the end of each day.
{% endhint %}

### Down payments and cancellations

Credits always cover 100% of the Reservation price at booking. PodCredits cannot take a partial deposit.

If your Club's terms include a non-refundable down payment, PodPlay can match it through the Reservation cancellation policy instead. For example, PodPlay can set the policy to refund 50% of the Credits when a Customer cancels within 24 hours of the Reservation. Tell your onboarding manager which refund rule matches your terms.

### Common issues

* **"Payment initiation failed: PSP PODCREDITS is not configured":** PodCredits is not connected to the Environment yet. Complete the PodCredits signup and approval, then connect the account in `Company Settings`.
* **`Token Status` shows Invalid or Expired:** Re-enter the PodCredits password and click `Save Changes`. Check that `User Email` and `Merchant Slug` match your PodCredits dashboard.
* **You cannot open `Company Settings`:** Only the Owner role can open it. Ask your onboarding manager to confirm your role.
* **A test booking will not go through:** Bookings need the PodCredits connection in place and your location and courts live. Adding Credits manually to a test Customer does not bypass this.
* **A staff member cannot add Credits:** Adding Credits needs the Manager role or above.
* **A Customer wants to pay a deposit only:** Deposits are not supported with Credits. Use the cancellation policy to apply your down payment terms.
* **A Customer wants to buy a Membership or a shop item:** The current PodCredits integration supports court Reservations and Coach Lessons only.

### FAQs

<details>

<summary>Can we opt out of Credits and collect payments manually after booking?</summary>

No. Clubs where Stripe is not available must run on Credits. Your team can still collect cash at the front desk and either book a single cash Reservation or add the matching Credits to the Customer's Profile.

</details>

<details>

<summary>Can Customers book as a guest without a Profile?</summary>

No. Every Customer creates a free Profile before booking. Sign-up is short and only happens once.

</details>

<details>

<summary>When are Credits subtracted from a Customer?</summary>

Immediately. When a Customer uses Credits, they are subtracted from the Profile right away. With a credit card on Stripe, the default system places a hold on the card instead of charging it immediately.

</details>

<details>

<summary>Can Credits be transferred from one Customer to another?</summary>

No. PodPlay does not move Credits from one Customer's Profile to another. Staff can subtract Credits from one Profile and add Credits to another Profile, and this is not a transfer. If the Customer asking for the move is in good standing, the Club decides how to support them based on its own operating procedures.

</details>

<details>

<summary>Can PodPlay set up the PodCredits account for us?</summary>

No. The Club signs up with PodCredits and creates its own account. PodPlay helps you connect the account to your Environment once it is approved.

</details>

<details>

<summary>What fees apply when Customers load Credits?</summary>

PodCredits sets its transaction fees. Your PodCredits contact can confirm the rates for your Club.

</details>

<details>

<summary>Can Customers top up their Wallet with cash?</summary>

No. Wallet top-ups accept QR Ph and card only. Your team can still take cash at the front desk and either book a single cash Reservation or add the matching Credits to the Customer's Profile.

</details>


---

# 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://docs.podplay.app/payments/magpie-podcredits.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.
