# PayPal payments inside a complete order > Plan a PayPal checkout integration around order states, account access, buyer communication, test payments, and reliable handoffs to fulfillment. Source: https://scayverstaging.1wp.site/integrations/paypal/ ![Person holding a credit card at a desk, using a computer with PayPal checkout on screen.](https://scayverstaging.1wp.site/wp-content/uploads/2026/07/sg-others-138069-hero.webp) A PayPal checkout integration should tell the buyer what they bought and tell your team when payment is complete, without treating a click as a paid order. [Talk to a Specialist](https://scayverstaging.1wp.site/talk-to-a-specialist/?form=book) [See every integration](https://scayverstaging.1wp.site/integrations/) **Integration type** [Payments](https://scayverstaging.1wp.site/integrations/?type=payments) **In this category** 2 Adding a payment button is only one step in selling online. The buyer needs to know what happens next, and your team needs to know whether payment completed before releasing a product, confirming a booking, or starting fulfillment. We define the website workflow and technical scope around that transaction. ## Decide what the buyer is paying for. Begin with a real offer. Is it a product with shipping, a fixed-price service, a deposit, or an invoice balance? Each has a different amount, confirmation message, cancellation path, and fulfillment owner. State those rules before choosing a button, hosted checkout, or platform extension. The website should show a clear description and total before the buyer commits. PayPal’s [checkout guidance](https://developer.paypal.com/studio/checkout/standard/integrate) describes an order creation and capture flow for direct integrations. A store platform may offer a different supported setup. The exact route depends on your website, PayPal account, region, and the payment experience you need. We would verify those details for the current environment rather than assume every PayPal option applies to every business. ## Separate approval from fulfillment. What should happen when a buyer approves a payment but the site does not receive a final result? What if a customer closes the browser before the thank-you page loads? Fulfillment should follow the verified transaction state, not the presence of a return-page visit. Define which system records the order, which event moves it to the next step, and how your team reconciles a mismatch. For a custom integration, PayPal documents [webhook events](https://developer.paypal.com/api/rest/webhooks) that can notify a site of payment-related changes. Such a connection needs a secure listener, appropriate event selection, validation, and a way to handle repeated or missed notifications. A business should also know where a human can inspect a transaction when the website and PayPal disagree. ## Test the PayPal checkout integration from both sides. Use a sandbox or other provider-supported test path before live transactions. Test an approved payment, a cancelled checkout, and an error that prevents completion. Check the buyer’s confirmation and the team’s order record. If refunds, subscriptions, taxes, or multiple currencies matter, treat those as explicit scope items rather than assume the basic checkout handles them. The business owns its payment account, policies, and decisions about taxes, refunds, and eligibility. Access to that account should be limited to the people who need it. We can map the website handoff and implementation requirements without implying merchant approval, a PayPal partnership, or a specific compliance outcome. ## Tell us where payment meets the next step. Show us what you sell and what your team must do after a buyer pays. We can help define the checkout and handoff questions before development begins. [Talk to a Specialist](https://scayverstaging.1wp.site/talk-to-a-specialist/) The build ## Building PayPal, and the friction that comes with it. ### How Scayver builds it. Scayver connects the PayPal business account to WooCommerce through the official gateway, configures API credentials, and enables the buttons and Pay Later where available. We test transactions, refunds, and the return flow back to the site. ### What goes wrong in practice. Incomplete return URLs leave orders unconfirmed. Account limitations or unverified business status can hold funds. Duplicate gateways confuse checkout if both old and new are active. Related ## More beside PayPal. - ### [Stripe](https://scayverstaging.1wp.site/integrations/stripe/) Secure card and subscription payments that just work at checkout. ### The services that use this integration. - #### [E-commerce Website Design](https://scayverstaging.1wp.site/services/design/e-commerce-website-design/) FAQ ## Questions about PayPal The things people ask on the first call. If yours is not here, ask us directly. [Ask us directly](https://scayverstaging.1wp.site/talk-to-a-specialist/?form=book) **Is a PayPal button enough for an online store?** Only if the surrounding order process is equally clear. You still need accurate totals, confirmations, fulfillment rules, and a way to handle failed or disputed transactions. **Can PayPal send payment events to another system?** PayPal offers event notifications for supported use cases. The relevant events, access, and receiving system must be scoped and tested. **Who should handle refunds?** Your business should define the policy and assign an authorized person. The website should communicate the path without inventing or overriding that policy.