This section also covers Workflow Studio, where you model your payment process as a visual workflow, and Autopilot, which routes each payment to the provider most likely to approve it. To take payments outside your checkout, see Payment Links and In-person payments.
Choose the right integration approach
Payrails offers several SDKs, each with a different balance of customization and PCI scope. Pick the approach that matches how much control you need over the checkout experience and how much card data your application handles.
What to consider
- Customization vs. ease of integration. For the simplest client-side setup that still uses Payrails orchestration, use the Drop-in SDK. For full control over the experience and presentation, use Elements or Secure Fields.
- PCI compliance. Every client-side SDK uses the Payrails PCI-compliant token vault, which minimizes your PCI scope. To collect and tokenize card data yourself, integrate with the API only.
- Adding new payment methods. The Drop-in SDK includes the frontend code for every payment method, so adding methods such as Apple Pay and Google Pay takes no frontend work on your side. The other approaches give you more control over where payment options appear in your checkout.
The following table compares what each approach supports. If you are unsure which one is right for you, contact your Payrails representative.
Next steps
To accept payments, connect at least one provider and enable the methods you want to offer. See Payment providers and Payment methods.
With more than one provider, Autopilot in Workflow Studio sends each payment to the provider most likely to approve it, and retries a decline on the next one.
After you choose an approach, start on the client-side implementation. The SDK guide explains how to get started, and each SDK type has its own guide: Drop-in, Elements, and Secure Fields.
If you prefer more frontend flexibility and choose not to use an SDK, refer to accepting payments via API. Last modified on November 13, 2026
