Embedded Checkout
Embed our checkout in your own web or mobile app. One component, every payment method.
Create the payment intent
confirm: false with your secret key, server-side. The response's client_secret is what you hand to the SDK — that and the publishable key are all the browser or app ever sees. Nothing in this request names a payment method: the checkout offers everything the account has enabled.
Who initiates the payment?
The two are different requests, not a flag on the same one.
The shopper is present and authorises the payment themselves. This is every other flow in this area.
One checkout, every method
EmbeddedThe SDK collects the payment method, handles whatever that method needs — a redirect, an inline QR, a wallet sheet — and confirms with the publishable key. The 22 methods in this catalogue all run through this one integration.
Right now the request narrows nothing, so the checkout shows every method the account has enabled.
allowed_payment_method_types
The one method-specific parameter in an SDK integration. Leave it empty and the checkout offers everything the account has enabled — including methods added later, with no code change.
Card
Bank transfer
Pay later
Wallet
Voucher
Crypto
After the shopper pays
The payment's payment_method_type tells you what was chosen. That is what decides the refund rule — the SDK has no say in it.
- PayShapOne refund only
- Scan to PayFull refunds only
- Capitec PayNo refunds
- PayflexFull or partial refunds
Full rules per method are listed under Customer payment methods.
Mobile SDK
The same `confirm: false` intent drives the iOS and Android SDKs. The app asks your server for one; here that server is this site.
https://playground.sandbox-next.peachpayments.com/api/create-msdk-intentReturns `clientSecret`, `ephemeralKey` and `publishableKey`. Add ?sessionId= to serve a payload you have edited on Modify MSDK intent.
This step doesn't require an API request.