> ## Documentation Index > Fetch the complete documentation index at: https://primer.io/docs/llms.txt > Use this file to discover all available pages before exploring further. # Fat Zebra > Process Card, Apple Pay, and Google Pay payments through Fat Zebra. Fat Zebra is an Australian payment gateway with global reach across 40+ countries. Connect Fat Zebra to Primer to process card payments, Apple Pay, Google Pay, and EFTPOS, and route them using Workflows. ## At a glance ### Supported payment methods | Payment method | Payment method type | Integration guide | | - | - | - | | Card | `PAYMENT_CARD` | [Card](https://primer.io/docs/connections/payment-methods/card/overview.md) | | Apple Pay | `APPLE_PAY` | [Apple Pay](https://primer.io/docs/connections/payment-methods/apple-pay/overview.md) | | Google Pay | `GOOGLE_PAY` | [Google Pay](https://primer.io/docs/connections/payment-methods/google-pay/overview.md) | Fat Zebra uses Primer's standard card form and Primer's native Apple Pay and Google Pay integrations, so no Fat Zebra-specific SDK code is required. ### Supported capabilities | Capability | Card | Apple Pay | Google Pay | | - | - | - | - | | Authorization and capture | Yes | Yes | Yes | | Refunds | Yes | Yes | Yes | | Partial refunds | Yes | Yes | Yes | | Merchant-initiated transactions | Yes | Yes | Yes | | Cancel / Void | No | No | No | ### 3D Secure Primer performs 3D Secure authentication using the [Perform 3DS action](https://primer.io/docs/workflows/apps/native-apps/primer-payments-app/perform-3ds-action.md) and passes the result to Fat Zebra. Fat Zebra does not run its own 3D Secure for payments processed through Primer. ## Get started with Fat Zebra ### Before you begin If this is your first connection, make sure to follow the [Get started guide](https://primer.io/docs/get-started/overview.md) to begin processing payments with Primer. You need a Fat Zebra sandbox account for testing and a separate production account. Contact Fat Zebra to provision both. > [!NOTE] > > Before going live, ask Fat Zebra support to enable **separate Authentication and Capture** on your production account. This is required for 3DS to work correctly with Primer. ### Credentials Fat Zebra provides your credentials on account setup. | Field | Where to find it | | - | - | | **Username** | Provided by Fat Zebra on account setup | | **Token password** | Provided by Fat Zebra on account setup | ### Configure in the Dashboard **1. Add Fat Zebra to your Dashboard** Go to [Integrations](https://dashboard.primer.io/integrations), select **New integration**, search for Fat Zebra, and enter your **Username** and **Token password**. **2. Activate the payment methods on the Checkout** Go to [Checkout](https://dashboard.primer.io/checkout) and activate the payment methods you want to offer. **3. Route payments with Workflows** In [Workflows](https://primer.io/docs/workflows/overview.md), select Fat Zebra in the **Authorize payment** action. Add the **Perform 3DS** action before authorization for card payments. ### Prepare the client session No additional fields are required beyond the standard `orderId`, `currencyCode`, `amount`, and `customer` fields. ## Considerations * **Australia-primary processor.** Fat Zebra's core market is Australia. Confirm currency and country support with Fat Zebra for other markets before going live. * **Dynamic response codes in sandbox.** The last two digits of the purchase amount control the response code (for example, AUD \$50.09 returns response code `09`). Use the designated test card numbers for straightforward approve or decline testing. * **Click to Pay test cards.** Only the designated Mastercard test card numbers work for Click to Pay in sandbox — arbitrary PANs cause the challenge to fail. * **Sandbox credentials begin with `TEST`.** Using sandbox credentials in production (or vice versa) will fail. ## Test in sandbox Connect your Fat Zebra test account (credentials begin with `TEST`) to your Primer Sandbox environment. > [tab] Card > > Use the following test cards. These cards trigger specific 3DS outcomes regardless of the purchase amount. > > | Card number | Brand | Scenario | > | - | - | - | > | `4000000000001018` | Visa | 3DS unsuccessful frictionless authentication | > | `5200000000001013` | Mastercard | 3DS unsuccessful frictionless authentication | > | `4000000000002446` | Visa | 3DS unsuccessful enrollment check (no liability shift) | > | `5200000000002037` | Mastercard | 3DS unsuccessful enrollment check (no liability shift) | > | `5186001700008785` | Mastercard | Click to Pay — receives PAN data | > [tab] Apple Pay > > Apple Pay payments use the same underlying card flow. Use a Visa or Mastercard from the sandbox card list in an Apple Pay-enabled test device. > [tab] Google Pay > > Use an Android device with a Mastercard or Visa from the Google Pay test card suite. > [tab] Merchant-initiated > > Make a customer-initiated card payment that saves the card, then create a merchant-initiated payment with the saved payment method. ## Go live Before switching to production, confirm that: 1. Fat Zebra support has enabled **separate Authentication and Capture** on your production account. 2. You have added Fat Zebra in your Primer **production** environment using your production **Username** and **Token password** (not `TEST` credentials). 3. The target currencies and countries are enabled on your Fat Zebra account. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.