--- title: Onboarding and Native Integration Differentiators | Shopware Community Hub description: >- Assess Shopware Payments fit, embedded onboarding in administration, and post-go-live controls for returns, rules, transactions, tax, and fraud. canonical_url: >- https://hub.shopware.com/learn/unit/onboarding-native-integration-differentiators --- # Onboarding and Native Integration Differentiators - **Use** **fit signals** and the core merchant profile as **self-checks** for whether **Shopware Payments** matches your shop. - **Explain** the **embedded onboarding flow** in **Shopware administration** and what becomes available after **PayPal** approval. - **Describe** **optimized**, **proactive**, and **pre-installed** onboarding principles and how they reduce setup friction. - **Identify** post-go-live **administration** controls—including **returns**, **Rule Builder**, **transaction history**, and **tax**—that extend beyond checkout capture. # Unit 2: Onboarding and Integration Differentiators **Strum & Co.** has seen the embedded payments pitch. Now their owner has a practical question: *"Does this actually fit how we operate — and what does switching look like in practice?"* That is what this unit is about. Not what **Shopware Payments** is — Unit 1 covered that — but whether it fits your shop, how **onboarding** works inside **Shopware administration**, and what you can control after go-live. --- ## Does Shopware Payments Fit Your Shop? This is not a question of who is "allowed" to use **Shopware Payments**. It is a question of where the product is optimized first — and where deeper discovery is worth the time before you commit. The **core profile** is **SMB and lower mid-market B2C and D2C merchants**: high adoption potential combined with relatively standardized payment needs. That is context for how features and markets roll out over time, not a ceiling on your project. Use the table below as a self-check: | You may align with the core profile when… | Plan deeper discovery when… | |------------------------------------------|----------------------------| | You use a **PayPal plugin** and want **less fragmentation** | You run **large-enterprise multi-PSP orchestration** already optimized for your model | | **PayPal** carries a meaningful share of your payment volume | You need **highly customized routing or settlement** beyond typical ecommerce flows | | Several integrations create unclear **ownership** and a patchwork checkout | **Marketplace or split-payout models** dominate and need specialist tooling | | **Reconciliation**, reporting, or issue resolution burns real manual time | **POS-first omnichannel** is the center of gravity — confirm physical retail and roadmap fit | | You are **expanding in the EU** and want repeatable configuration | **Regulated industries** need bespoke compliance beyond standard onboarding | | You are **replatforming** or rebuilding checkout | A mature **in-house payments team** treats multi-PSP optimization as core IP | | **Founder-led or growth-stage** teams value speed over bespoke complexity | There is no forcing function — "if it isn't broken" can be rational until triggers appear | --- ## How Onboarding Works **Shopware Payments** provides a fully embedded **merchant onboarding flow** through a dedicated payments section in **Shopware administration**. There are no external setup portals or manual credential handling — the flow stays inside **Shopware** from first activation through go-live. The onboarding process supports: - **Connecting an existing PayPal Business account** or creating a new one if you do not have one yet - **Automated and secure credential exchange** between **Shopware** and **PayPal** — keys and connection details are not copied by hand Three design principles shape how onboarding behaves: **Optimized** — **Shopware-held merchant data** is reused where possible, reducing redundant input. Onboarding runs in context — including inside the **First Run Wizard** — rather than sending merchants through a disconnected sequence of screens. **Proactive** — Where applicable, **Shopware Account** supports **pre-onboarding** during license negotiations, so **Shopware Payments** can be operational sooner when a new shop is created. **Pre-installed** — **Shopware Payments** is already part of **Shopware 6**. Merchants on a current version get the integration without installing an extension. Relevant capabilities are visible but inactive until onboarding completes — including on the **payment methods** page and in adjacent areas such as **tax**, **returns**, and **new POS sales channels**. Once onboarding completes and **PayPal** approves the connected account, **Shopware Payments** becomes available in checkout — including **authorization**, **capture**, **refunds**, and **order status synchronization** with your **Shopware** orders. --- ## Operations and Controls After go-live, **Shopware Payments** adds operational depth that typical plugins do not provide natively: - **Intelligent configuration** — helps match **payment methods** to markets and demographics, and assists when new **sales channels** are created - **Advanced fraud protection** — combines **PayPal's** protections with **Shopware Rule Builder** rules so merchants can control when certain payment or financing options appear - **Streamlined return management** — links **refunds** to Shopware's **return flows** so adjustments are handled in **administration** rather than an external portal - **Comprehensive transaction history** — a **payment-centric view** beside orders, including traceable **transactions** that support cases like multiple orders in one payment or delivery flow - **Integrated tax management** — tax calculation folded into **Shopware Payments** with configuration in **administration**, reducing reliance on separate tax extensions - **Rule Builder and Flow Builder extensions** — additional queries, triggers, and actions for processes like **credit checks**, **disputes**, and **automated refunds** - **Customer credit** — supports credit balance scenarios and **voucher-style** use cases --- From there, you'll see where payments connect to returns, Rule Builder, and reporting when order and payment data share Shopware's model—not only at checkout.