> 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/owners-playbook/build-your-club/configure-podcredits-magpie-psp-integration.md). # Configure PodCredits (MagPie PSP) Integration PodCredits is a Payment Service Provider (PSP) integration that lets your facility use a local payment provider for virtual credits and related payments. When this integration is enabled and the feature flag is turned on, Customers can use the PodCredits flow in the app instead of Stripe for eligible transactions. Use this when your organization has a PodCredits/MagPie agreement and you need to connect your PodPlay venue to it. ## Where to find PodCredits settings * Open **Company Settings** for your venue (or the tenant you manage) * Click the **Integrations** tab * Scroll to the **PodCredits/MagPie PSP** section ![](/files/3TCulWB7rooZZTeibBIY) ## Enable or disable the integration * In the **PodCredits/MagPie PSP** section, find **PodCredits Integration** * Use the toggle to turn the integration **on** (checkmark) or **off** (X) When the integration is off, PodCredits will not be used for payments even if the feature flag is enabled. ## Enter PodCredits account details * **User Email**: Enter the email address associated with your PodCredits account. The system validates that it is a valid email. * **Merchant Slug**: Enter the PodCredits merchant identifier (the slug provided by PodCredits/MagPie). * **Password**: Enter the PodCredits account password. Use **Edit PodCredits Password** to show or change the stored password. Changing the password will invalidate the current access token; the system will obtain a new one when needed. ![](/files/3TCulWB7rooZZTeibBIY) **PLEASE NOTE:** PodCredits account password is stored securely. Changing it here will invalidate the current access token used for API calls. ## Check token status Below the password field, **Token Status** shows whether the current PodCredits access token is valid and when it expires. * **Valid** (green): The token is active and the integration can process payments. * **Invalid or Expired** (red): Update the password or re-enter credentials so the system can obtain a new token. If the token is invalid or expired, payment flows that rely on PodCredits may fail until the configuration is updated and saved. ## Use the local PSP and hide Stripe in the app To have Customers use PodCredits (local PSP) instead of Stripe in the app: * Open the **Features** tab in Company Settings * In the **Payments** group, enable **Use local PSP and Skip Stripe** When this feature is enabled, the app uses the local payment provider (PodCredits when configured) and Stripe payment options are hidden from Customers. ![](/files/5fiIFdZkk00pqVTEbbqZ) ## Save or discard changes * To keep your PodCredits settings: Click **Save Changes** at the top of the Company Settings page. All sections (including PodCredits) are saved together. * To undo edits: Click **Discard Changes** to restore the last saved values. If configuration fails to load, a **Retry** button appears so you can try loading again. ### Tips * Ensure User Email and Merchant Slug match the values provided by PodCredits/MagPie. * If you see "Invalid or Expired" token status after saving, re-enter the password and save again. * Do not enable **Use local PSP and Skip Stripe** until PodCredits is configured and token status is **Valid**, or Customers may not have a working payment method. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podplay.app/owners-playbook/build-your-club/configure-podcredits-magpie-psp-integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.