--- updatedAt: 2026-10-16T16:16:24.000Z agentTools: projectIndex: https://developer.peachpayments.com/llms.txt --- # Payment methods # Introduction To learn more about the payment methods, see the [Peach Payments website](https://www.peachpayments.com/payment-method). - Enable more payment methods on your Peach Payments account using the [Dashboard](https://developer.peachpayments.com/docs/manage-payment-methods#activate-a-payment-method). - [Capitec Pay](https://developer.peachpayments.com/docs/pp-payment-methods#capitec-pay) and [Absa Pay](https://developer.peachpayments.com/docs/pp-payment-methods#absa-pay) have certain restrictions for high-risk merchants. - For more information on payment types, see the [payments reference material](https://developer.peachpayments.com/docs/reference-payments). - For details on how to test payment methods in the sandbox environment, see the [test and go live procedure](https://developer.peachpayments.com/docs/reference-test-and-go-live). # Choose the right product The Peach Payments product portfolio contains multiple products suited to different requirements. The following diagram can help you choose which products are right for your requirements. If you're performing a new integration, use [Peach Orchestration](https://playground.peachpayments.com/). The Payments API does not support card payments, so existing Payments API merchants who want to accept card payments must use [Checkout](https://developer.peachpayments.com/docs/checkout-embedded) in conjunction with Payments API. ```mermaid %%{init: {'theme': 'base', 'htmlLabels': false, 'themeVariables': { 'primaryColor': '#EE8031', 'secondaryColor':'#EE8031', 'lineColor':'#EE8031','textColor':'#EE8031', 'fontFamily': 'Inter' }}}%% flowchart TD A[Do you have an eCommerce store, physical store, or no store at all?] -->|No store|B[Use Payment Links, Payment Page, Xero, or MOTO.] A -->|eCommerce store|C[Is your eCommerce store built using Ecwid, Gravity Forms, Magento, nopCommerce, OpenCart, Shopify, Wix, or WooCommerce?] A -->|Physical store|P[Use POS device.] C -->|Yes|D[Use one of our payment extensions.] C -->|No|E[Do you want to customise the customer's payment flow?] E -->|Yes|G["Use Peach Orchestration's Server-to-Server."] E -->|No|F[Do you want to embed checkout on your website or redirect to Peach Payments?] F -->|Redirect|I["Use Peach Orchestration's Hosted Checkout."] F -->|Embed|H["Use Peach Orchestration's Embedded Checkout."] ``` # South Africa This table does not cover Peach Orchestration. For the payment methods that Peach Orchestration supports, see the [payment methods page in the Peach Orchestration playground](https://playground.peachpayments.com/operate/payment-methods). | Category | Payment method (`parameter`) | Currencies | Integrations | Refunds | Other payment types | | :------------------- | :----------------------------------------------------------------------------------------------------- | :-------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------ | :-----------------------------------------------------------------------------------------: | :------------------- | | Card | Visa (`CARD`) | ZAR | Embedded Checkout, Hosted Checkout, Payment Links, Payment Page, payment extensions, POS, MOTO, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB, RG\*, PA, CP\*\* | | | Mastercard (`CARD`) | ZAR | Embedded Checkout, Hosted Checkout, Payment Links, Payment Page, payment extensions, POS, MOTO, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB, RG\*, PA, CP\*\* | | | Amex (`CARD`) | ZAR | Embedded Checkout, Hosted Checkout, Payment Links, Payment Page, payment extensions, POS, MOTO, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB, RG\*, PA, CP\*\* | | | Diners (`CARD`) | ZAR | Embedded Checkout, Hosted Checkout, Payment Links, Payment Page, payment extensions, MOTO, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB, RG\*, PA, CP\*\* | | Card, multi-currency | Visa, Mastercard (`CARD`) | Multiple, if using Absa Planet Payments | Embedded Checkout, Hosted Checkout, Payment Links, Payment Page, payment extensions, MOTO, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB, RG\*, PA, CP\*\* | | EFT | [PayShap](https://developer.peachpayments.com/docs/pp-payment-methods#payshap) (`PAYSHAP`) | ZAR | Embedded Checkout, Hosted Checkout, Payments API, Payment Links, Payment Page, payment extensions, POS | ✅
Full or partial (one refund only) | DB | | | [Pay by Bank](https://developer.peachpayments.com/docs/pp-payment-methods#/pay-by-bank) (`PAYBYBANK`) | ZAR | Embedded Checkout, Hosted Checkout, Payment Links, Payment Page, payment extensions, POS | ❌ | DB | | | [Capitec Pay](https://developer.peachpayments.com/docs/pp-payment-methods#capitec-pay) (`CAPITECPAY`) | ZAR | Embedded and Hosted Checkout (via Pay by Bank), Payments API, Payment Links, Payment Page, payment extensions, POS | ❌ | DB | | | [Absa Pay](https://developer.peachpayments.com/docs/pp-payment-methods#absa-pay) (`ABSAEFT`) | ZAR | Embedded and Hosted Checkout (via Pay by Bank), Payments API (via Peach EFT), Payment Links, Payment Page, payment extensions, POS | ❌ | DB | | | [Peach EFT](https://developer.peachpayments.com/docs/pp-payment-methods#peach-eft) (`PEACHEFT`) | ZAR | Payments API | ❌ | DB | | Buy now, pay later | [Payflex](https://developer.peachpayments.com/docs/pp-payment-methods#payflex) (`PAYFLEX`) | ZAR | Embedded Checkout, Hosted Checkout, Payments API, Payment Links, Payment Page, payment extensions, POS | ✅
Full or partial | DB | | | [ZeroPay](https://developer.peachpayments.com/docs/pp-payment-methods#zeropay) (`ZEROPAY`) | ZAR | Embedded Checkout, Hosted Checkout, Payments API, Payment Links, Payment Page, payment extensions, POS | ❌ | DB | | | Float (`FLOAT`) | ZAR | Embedded Checkout, Hosted Checkout, Payments API, Payment Links, Payment Page, payment extensions, POS | ✅
Full or partial | DB | | | Happy Pay (`HAPPYPAY`) | ZAR | Embedded Checkout, Hosted Checkout, Payments API, Payment Links, Payment Page, payment extensions, POS | ✅
Full or partial | DB | | | PayJustNow | ZAR | POS | ✅
Full or partial
(POS only; eCommerce not yet supported) | DB | | QR code | [Scan to Pay](https://developer.peachpayments.com/docs/pp-payment-methods#scan-to-pay) (`MASTERPASS`) | ZAR | Embedded Checkout, Hosted Checkout, Payments API, Payment Links, Payment Page, payment extensions, POS | ✅
[Full only](https://developer.peachpayments.com/docs/pp-payment-methods#scan-to-pay) | DB | | Wallet | [Apple Pay](https://developer.peachpayments.com/docs/pp-payment-methods#apple-pay) (`APPLE PAY`) | ZAR | Embedded Checkout, Hosted Checkout, Embedded Express, Payment Links, Payment Page, payment extensions, POS, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB | | | [Google Pay](https://developer.peachpayments.com/docs/pp-payment-methods#google-pay) (`GOOGLEPAY`) | ZAR | Embedded Checkout, Hosted Checkout, Embedded Express, Payment Links, Payment Page, payment extensions, POS, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB | | | [Samsung Pay](https://developer.peachpayments.com/docs/pp-payment-methods#samsung-pay) (`SAMSUNGPAY`) | ZAR | Embedded Checkout, Hosted Checkout, Embedded Express, Payment Links, Payment Page, payment extensions, POS, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB | | | PayPal (`PAYPAL`) | USD, GBP, and EUR | Hosted Checkout, Payment Links, payment extensions, POS | ✅
Full or partial | DB, RG\* | | Voucher | 1Voucher (`1FORYOU`) | ZAR | Embedded Checkout, Hosted Checkout, Payments API, Payment Links, Payment Page, payment extensions, POS | ✅
Full or partial | DB | | Alternative credit | [Mobicred](https://developer.peachpayments.com/docs/pp-payment-methods#mobicred) (`MOBICRED`) | ZAR | Embedded Checkout, Hosted Checkout, Payments API, Payment Links, Payment Page, payment extensions, POS | ✅
Full or partial | DB | | | RCS credit and store cards (`RCS`) | ZAR | Embedded Checkout, Hosted Checkout, Payments API, Payment Links, Payment Page, payment extensions, POS | ✅
Full or partial | DB | | | A+ store cards (`APLUS`) | ZAR | Embedded Checkout, Hosted Checkout, Payment Links, Payment Page, payment extensions, POS | ✅
Full or partial | DB | | Crypto | [MoneyBadger](https://developer.peachpayments.com/docs/pp-payment-methods#moneybadger) (`MONEYBADGER`) | ZAR | Embedded Checkout, Hosted Checkout, Payments API, Payment Links, Payment Page, payment extensions, POS | ✅
Full or partial | DB | \* Embedded Checkout and Hosted Checkout do not support the RG payment type, but you can [tokenise](https://developer.peachpayments.com/docs/checkout-tokenisation) a card while performing a DB or PA. \*\* Follow [this guide](https://developer.peachpayments.com/docs/card-manage-payments#capture-a-preauthorisation) to capture a preauthorisation. To refund a transaction, use the [Dashboard](https://developer.peachpayments.com/docs/dashboard-transactions#refund-a-debit) or the relevant API: * [Embedded Checkout and Hosted Checkout](https://developer.peachpayments.com/docs/checkout-refund) * [Payments API](https://developer.peachpayments.com/reference/refund) Depending on the payment method, refunds complete in: * Card and BNPL (buy now, pay later) payment methods: Up to 14 business days * PayShap: Depends on the bank, with some banks processing refunds immediately * MoneyBadger: Immediately * Other payment methods: Up to 30 days For payment methods that do not support refunds, you must process refunds manually. One way of doing this is to contact your customer to request their bank account details for an EFT transfer. For more information on the requirements for a multi-currency merchant account with Absa, see the [support knowledge base](https://support.peachpayments.com/support/solutions/articles/47001143548-absa-multi-currency-merchant-account-criteria). ## PayShap PayShap enables customers to make instant payments using their banking apps. PayShap has the following limitations: - Supports one refund per transaction only. If you perform a partial refund, you cannot perform another refund later. - Limited to specific participating banks with different transaction limits. | Bank | Support status | Transaction limit | | :------------- | :--------------- | :---------------- | | Absa | ✅ Supported | R3,000 | | Discovery Bank | ✅ Supported | R3,000 | | FNB | ✅ Supported | R3,000 | | Nedbank | ✅ Supported | R50,000 | | TymeBank | ✅ Supported | R5,000 | | African Bank | ❌ Not supported | Not applicable | | Capitec | ❌ Not supported | Not applicable | | Investec | ❌ Not supported | Not applicable | | Standard Bank | ❌ Not supported | Not applicable | For details on how to test PayShap in the sandbox environment, see the [test and go live procedure](https://developer.peachpayments.com/docs/reference-test-and-go-live#payshap). ## Pay by Bank Pay by Bank offers the EFT payment method for the same banks that [Peach EFT](https://developer.peachpayments.com/docs/pp-payment-methods#/peach-eft) does, as well as Capitec Pay and Absa Pay. Pay by Bank is only available on Embedded Checkout and Hosted Checkout. When attempting to pay large amounts using Pay by Bank, your customers should ensure that their bank payment limits are high enough to cover the amount. For details on how to test Pay by Bank in the sandbox environment, see the [test and go live procedure](https://developer.peachpayments.com/docs/reference-test-and-go-live#pay-by-bank). ## Capitec Pay For Checkout, Capitec Pay is included in [Pay by Bank](https://developer.peachpayments.com/docs/pp-payment-methods#pay-by-bank) user interface. Capitec categorises merchants as either high or low risk. The following table describes the different options available for merchants, depending on their risk category. | Risk category | Product | Notes | | :------------ | :------------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------- | | Low | All products | Supports paying with ID and phone number. | | High | Embedded Checkout and Hosted Checkout API, Payments API | Supports paying with merchant-provided verified ID that the customer cannot edit. Does **not** support paying with phone number. | * For Checkout, you must provide the verified ID in the `customer.idNumber` parameter. * For Payments API, you must provide the verified ID in the following format: ```json "virtualAccount": { "type": "IDNUMBER", "accountId": "9999999999999" } ``` - High-risk merchants using Payment Links, Payment Page, or a payment extension cannot use Capitec Pay as there is no way for them to provide the ID number in payment requests. - Capitec Pay does not support paying with passport numbers for low- or high-risk merchants. For details on how to test Capitec Pay in the sandbox environment, see the [test and go live procedure](https://developer.peachpayments.com/docs/reference-test-and-go-live#capitec-pay). ## Absa Pay - For Checkout, Absa Pay is included in [Pay by Bank](https://developer.peachpayments.com/docs/pp-payment-methods#pay-by-bank) user interface. - For Payments API, use `PEACHEFT` for the `paymentBrand` and use the `virtualAccount` array to specify `ABSAEFT` as the `processor`. To pay with Absa Pay, your customers **must** have the Absa banking app. For more information on registration, see [Absa: How to register for the Absa banking app](https://www.youtube.com/watch?v=H05NTj2ZhCI). Absa categorises merchants as either high or low risk. The following table describes the different options available for merchants, depending on their risk category. | Risk category | Product | Notes | | :------------ | :------------------------------------------------------ | :-------------------------------------------------------------------------------- | | Low | All products | Supports paying with ID. | | High | Embedded Checkout and Hosted Checkout API, Payments API | Supports paying with merchant-provided verified ID that the customer cannot edit. | * For Checkout, you must provide the verified ID in the `customer.idNumber` parameter. * For Payments API, you must provide the verified ID in the following format: ```json "virtualAccount": [ { "processor": "ABSAEFT", "identifier": [ { "type": "IDNUMBER", "accountId": "9999999999999" } ] } ] ``` - High-risk merchants using Payment Links, Payment Page, or a payment extension cannot use Absa Pay as there is no way for them to provide the ID number in payment requests. - Absa Pay does not support paying with passport numbers for low- or high-risk merchants. For details on how to test Absa Pay in the sandbox environment, see the [test and go live procedure](https://developer.peachpayments.com/docs/reference-test-and-go-live#absa-pay). ## Peach EFT Peach EFT enables you to offer the EFT payment method for multiple banks, including Absa, Nedbank, FNB, Standard Bank, Investec, Bidvest Bank, and African Bank. Peach EFT is only available on Payments API. When attempting to pay large amounts using Peach EFT, your customers should ensure that their bank payment limits are high enough to cover the amount. For details on how to test Peach EFT in the sandbox environment, see the [test and go live procedure](https://developer.peachpayments.com/docs/reference-test-and-go-live#peach-eft). ## Scan to Pay For Scan to Pay, refunds are not allowed on debit cards. You can process a reversal on the debit card using the Scan to Pay service, but you must complete it before six hours have elapsed since the original transaction. Multiple [Scan to Pay](https://developer.peachpayments.com/docs/reference-test-and-go-live#scan-to-pay), banking, and payments mobile apps, including the [Nedbank Money](https://play.google.com/store/apps/details?id=za.co.nedbank), [Standard Bank](https://play.google.com/store/apps/details?id=com.sbg.mobile.phone), [Absa Banking App](https://play.google.com/store/apps/details?id=com.barclays.absa.banking), [Capitec Bank](https://play.google.com/store/apps/details?id=capitec.acuity.mobile.prod), [FNB Banking App](https://play.google.com/store/apps/details?id=za.co.fnb.connect.itt), [RMB Private Bank App](https://play.google.com/store/apps/details?id=za.co.fnb.connect.rmbpb), [Masterpass Scan to Pay](https://play.google.com/store/apps/details?id=com.oltio.capitec.masterpass), [VodaPay](https://play.google.com/store/apps/details?id=za.co.vodacom.vodapay), [Telkom Pay Digital Wallet](https://play.google.com/store/apps/details?id=za.co.telkom.consumer), and [Spot Money - Mobile Banking](https://play.google.com/store/apps/details?id=za.co.wigroup.spot.prod) support Scan to Pay QR codes. Multiple mobile apps can pay Scan to Pay QR codes. For details on how to test Scan to Pay in the sandbox environment, see the [test and go live procedure](https://developer.peachpayments.com/docs/reference-test-and-go-live#scan-to-pay). ## Apple Pay To offer Apple Pay to your customers, you must: * Have an FNB, Nedbank, or Standard Bank merchant account. * Have card enabled on your Peach Payments account. Embedded Checkout and Hosted Checkout support Apple Pay on: * iOS and macOS devices (iPhone, iPad, Macs, and so on): All browsers, including Safari, Chrome, Firefox, and so on. * Windows devices: Firefox and all modern, Chromium-based browsers, including Google Chrome, Microsoft Edge, Opera, and so on. To scan the QR code, customers must use a mobile device running iOS 18 or later. Embedded Express supports Apple Pay on: * iOS devices (iPhone, iPad, and so on): Safari and Chrome. * macOS devices (Macs and so on): Safari. * Windows devices: Not supported. > 🚧 > > The support for Apple Pay on non-Safari browsers might change in the future. For details on how to test Apple Pay in the sandbox environment, see the [test and go live procedure](https://developer.peachpayments.com/docs/reference-test-and-go-live#apple-pay). ## Google Pay To offer Google Pay to your customers, you must: * Have signed up with Google Pay. * Have an Absa, FNB, Nedbank, or Standard Bank merchant account. * Have card enabled on your Peach Payments account. * [Send Peach Payments support](https://support.peachpayments.com/support/tickets/new?ticket_form=log_a_support_ticket) your Google Pay merchant ID if you're using Embedded Checkout. If you load Checkout in an Android WebView, enable the Payment Request API so Google Pay can complete. See [Configure Android WebView for Google Pay and Samsung Pay](https://developer.peachpayments.com/docs/checkout-android-webview-wallets). For details on how to test Google Pay in the sandbox environment, see the [test and go live procedure](https://developer.peachpayments.com/docs/reference-test-and-go-live#google-pay). ## Samsung Pay To offer Samsung Pay to your customers, you must: * Have signed up with Samsung Pay. * Have a Nedbank or Standard Bank merchant account. * Have card enabled on your Peach Payments account. If you load Checkout in an Android WebView, support multiple windows and handle Samsung's URL schemes so Samsung Pay can complete. See [Configure Android WebView for Google Pay and Samsung Pay](https://developer.peachpayments.com/docs/checkout-android-webview-wallets). Embedded Express supports Samsung Pay on: * Samsung devices: All browsers. ## Payflex Payflex supports payments between R10 and R50,000 by default. To request a higher limit, [contact support](https://support.peachpayments.com/support/tickets/new?ticket_form=log_a_support_ticket). See the [Payflex documentation](https://docs.payflex.co.za/docs/widgets) for details on how to configure the Payflex widget. You can also use the widget on the following eCommerce platforms: * [Shopify](https://docs.payflex.co.za/docs/widgets#shopify-widget) * [Shopify with the Dawn theme](https://support.peachpayments.com/support/solutions/articles/47001219692-configure-shopify-dawn-theme-with-a-payflex-calculator) * [WooCommerce](https://docs.payflex.co.za/docs/widgets#woocommerce-widget) For details on how to test Payflex in the sandbox environment, see the [test and go live procedure](https://developer.peachpayments.com/docs/reference-test-and-go-live#payflex). ## ZeroPay The minimum amount you can pay using ZeroPay is R30. Use the following files to configure the ZeroPay instalment calculator depending on your eCommerce platform: * [Basic instalment calculator](https://get.peachpayments.com/hubfs/instalment-calculators/ZeroPayInstalment_Basic.zip) * [Magento](https://get.peachpayments.com/hubfs/instalment-calculators/ZeroPayInstalment_Magento.zip) * [Shopify](https://get.peachpayments.com/hubfs/instalment-calculators/ZeroPayInstalment_Shopify.zip) * [WooCommerce](https://get.peachpayments.com/hubfs/instalment-calculators/ZeroPayInstalment_Wordpress.zip) For details on how to test ZeroPay in the sandbox environment, see the [test and go live procedure](https://developer.peachpayments.com/docs/reference-test-and-go-live#zeropay). ## Float Float supports payments between R1 and R99,000. Use the following files to integrate the Float widget depending on your eCommerce platform: * [Shopify](https://get.peachpayments.com/hubfs/instalment-calculators/FloatWidget_Shopify.pdf) * [WooCommerce](https://get.peachpayments.com/hubfs/instalment-calculators/FloatWidget_Woocommerce.zip) For details on how to test Float in the sandbox environment, see the [test and go live procedure](https://developer.peachpayments.com/docs/reference-test-and-go-live#float). ## Happy Pay See the [Happy Pay documentation](https://widgets.happypay.co.za/peach.htm) for details on how to configure Happy Pay's payment widget in HTML or on Shopify. For WooCommerce, use [this file](https://get.peachpayments.com/hubfs/instalment-calculators/happypay-widget.zip). For details on how to test Happy Pay in the sandbox environment, see the [test and go live procedure](https://developer.peachpayments.com/docs/reference-test-and-go-live#happy-pay). ## Mobicred See the [Mobicred documentation](https://mobicred.co.za/app-widget/instalment) for details on how to configure the Mobicred instalment widget. The widget also supports multiple eCommerce platforms, including Magento, OpenCart, Shopify, and WooCommerce. See the **Integrations** section for more details. For details on how to test Mobicred in the sandbox environment, see the [test and go live procedure](https://developer.peachpayments.com/docs/reference-test-and-go-live#mobicred). ## MoneyBadger MoneyBadger enables you to accept crypto payments from Bitcoin Lightning Network, Luno, VALR, Binance, and Bybit wallets. ### Refunds * You can only refund amounts equal to or more than R25 which also applies to partial refunds. * For Bitcoin Lightning Network wallets (this is not required for Luno, VALR, Binance, or Bybit), customers must provide their wallet address during the initial payment process if they want to be able to refund their transaction later. If they don't, attempts to refund the transaction fail with the `800.100.195` response code. Customers with Bitcoin Lightning Network wallets must provide their wallet address during the initial payment process if they want to be able to request a refund later. Ensure that your customers are aware of the refund limit and that for Bitcoin Lightning Network wallets, that they must provide their wallet address during the initial payment if they want to be able to request a refund later. Peach Payments bases the refund amount on the item's Rand (ZAR) price at the time that the customer bought it. Peach Payments converts the Rand value to crypto using the exchange rate at the time of the refund which means that the customer might get a different amount of crypto back than they first paid. For example: * Your customer bought an item for R100, which cost them 0.00004 Bitcoin at the time. * The refund value: R100 * What the customer gets back when they request the refund: R100 worth of Bitcoin at the current exchange rate. For details on how to test MoneyBadger in the sandbox environment, see the [test and go live procedure](https://developer.peachpayments.com/docs/reference-test-and-go-live#moneybadger). # Kenya This table does not cover Peach Orchestration. For the payment methods that Peach Orchestration supports, see the [payment methods page in the Peach Orchestration playground](https://playground.peachpayments.com/operate/payment-methods). | Category | Payment method (`parameter`) | Currencies | Integrations | Refunds | Other payment types | | :------------------- | :------------------------------- | :--------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------- | :--------------------: | :------------------- | | Card | Visa (`CARD`) | KES and depending on the acquirer, EUR and USD | Embedded Checkout, Hosted Checkout, Payment Links, Payment Page, payment extensions, MOTO, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB, RG\*, PA, CP\*\* | | | Mastercard (`CARD`) | KES and depending on the acquirer, EUR and USD | Embedded Checkout, Hosted Checkout, Payment Links, Payment Page, payment extensions, MOTO, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB, RG\*, PA, CP\*\* | | | Amex (Equity Bank only) (`CARD`) | KES | Embedded Checkout, Hosted Checkout, Payment Links, Payment Page, payment extensions, MOTO, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB, RG\*, PA, CP\*\* | | Card, multi-currency | Visa, Mastercard (`CARD`) | Multiple, depending on the acquirer | Embedded Checkout, Hosted Checkout, Payment Links, Payment Page, payment extensions, MOTO, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB, RG\*, PA, CP\*\* | | Mobile money | M-PESA (`MPESA`) | KES | Embedded Checkout, Hosted Checkout, Payments API, Payment Links, Payment Page, payment extensions | ❌ | DB | \* Embedded Checkout and Hosted Checkout do not support the RG payment type, but you can [tokenise](https://developer.peachpayments.com/docs/checkout-tokenisation) a card while performing a DB or PA. \*\* Follow [this guide](https://developer.peachpayments.com/docs/card-manage-payments#capture-a-preauthorisation) to capture a preauthorisation. To refund a transaction, use the [Dashboard](https://developer.peachpayments.com/docs/dashboard-transactions#refund-a-debit) or the relevant API: * [Embedded Checkout and Hosted Checkout](https://developer.peachpayments.com/docs/checkout-refund) * [Payments API](https://developer.peachpayments.com/reference/refund) Depending on the payment method, refunds complete in: * Card: Up to 14 business days * Other payment methods: Up to 30 days For payment methods that do not support refunds, you must process refunds manually. One way of doing this is to contact your customer to request their bank account details for an EFT transfer. # Mauritius This table does not cover Peach Orchestration. For the payment methods that Peach Orchestration supports, see the [payment methods page in the Peach Orchestration playground](https://playground.peachpayments.com/operate/payment-methods). | Category | Payment method | Currencies | Integrations | Refunds | Other payment types | | :------------------- | :------------------------------------------------------------------------------------------------- | :--------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------- | :--------------------: | :------------------- | | Card | Visa (`CARD`) | MUR and depending on the acquirer, EUR and USD | Embedded Checkout, Hosted Checkout, Payment Links, Payment Page, payment extensions, MOTO, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB, RG\*, PA, CP\*\* | | | Mastercard (`CARD`) | MUR and depending on the acquirer, EUR and USD | Embedded Checkout, Hosted Checkout, Payment Links, Payment Page, payment extensions, MOTO, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB, RG\*, PA, CP\*\* | | | Amex (`CARD`) | MUR and depending on the acquirer, EUR and USD | Embedded Checkout, Hosted Checkout, Payment Links, Payment Page, payment extensions, MOTO, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB, RG\*, PA, CP\*\* | | | Diners (`CARD`) | MUR and depending on the acquirer, EUR and USD | Embedded Checkout, Hosted Checkout, Payment Links, Payment Page, payment extensions, MOTO, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB, RG\*, PA, CP\*\* | | Card, multi-currency | Visa, Mastercard (`CARD`) | Multiple, depending on the acquirer | Embedded Checkout, Hosted Checkout, Payment Links, Payment Page, payment extensions, MOTO, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB, RG\*, PA, CP\*\* | | Wallet | [Apple Pay](https://developer.peachpayments.com/docs/pp-payment-methods#apple-pay-1) (`APPLE PAY`) | MUR and USD | Embedded Checkout, Hosted Checkout, Embedded Express, Payment Links, Payment Page, payment extensions, Server-to-Server, Mobile SDK V1 | ✅
Full or partial | DB | | | blink by Emtel (`BLINKBYEMTEL`) | MUR | Embedded Checkout, Hosted Checkout, Payments API, Payment Links, Payment Page, payment extensions | ❌ | DB | | | MCB Juice (`MCBJUICE`) | MUR | Embedded Checkout, Hosted Checkout, Payments API, Payment Links, Payment Page, payment extensions | ❌ | DB | | | PayPal (`PAYPAL`) | USD, GBP, and EUR | Hosted Checkout, Payment Links, payment extensions | ✅
Full or partial | DB, RG\* | | QR code | MauCAS (`MAUCAS`) | MUR | Embedded Checkout, Hosted Checkout, Payments API, Payment Links, Payment Page, payment extensions, POS | ❌ | DB | \* Embedded Checkout and Hosted Checkout do not support the RG payment type, but you can [tokenise](https://developer.peachpayments.com/docs/checkout-tokenisation) a card while performing a DB or PA. \*\* Follow [this guide](https://developer.peachpayments.com/docs/card-manage-payments#capture-a-preauthorisation) to capture a preauthorisation. To refund a transaction, use the [Dashboard](https://developer.peachpayments.com/docs/dashboard-transactions#refund-a-debit) or the relevant API: * [Embedded Checkout and Hosted Checkout](https://developer.peachpayments.com/docs/checkout-refund) * [Payments API](https://developer.peachpayments.com/reference/refund) Depending on the payment method, refunds complete in: * Card: Up to 14 business days * Other payment methods: Up to 30 days For payment methods that do not support refunds, you must process refunds manually. One way of doing this is to contact your customer to request their bank account details for an EFT transfer. ## Apple Pay To offer Apple Pay to your customers, you must: * Have an MCB or Absa Mauritius merchant account. * Have card enabled on your Peach Payments account. Embedded Checkout and Hosted Checkout support Apple Pay on: * iOS and macOS devices (iPhone, iPad, Macs, and so on): All browsers, including Safari, Chrome, Firefox, and so on. * Windows devices: Firefox and all modern, Chromium-based browsers, including Google Chrome, Microsoft Edge, Opera, and so on. To scan the QR code, customers must use a mobile device running iOS 18 or later. Embedded Express supports Apple Pay on: * iOS devices (iPhone, iPad, and so on): Safari and Chrome. * macOS devices (Macs and so on): Safari. * Windows devices: Not supported. > 🚧 > > The support for Apple Pay on non-Safari browsers might change in the future. For details on how to test Apple Pay in the sandbox environment, see the [test and go live procedure](https://developer.peachpayments.com/docs/reference-test-and-go-live#apple-pay).