What we do
Tools
Industries
Department
How we workLet's talk →
Home/PayPal/PayPal Developer Dashboard
PayPal API

The PayPal Developer Dashboard: Where Your Keys, Sandbox Accounts and Webhooks Are

The PayPal developer dashboard lives at developer.paypal.com and uses your normal PayPal login. It's where you get the Client ID and Secret a plugin or custom checkout asks for, the fake buyer and seller accounts you test with, and the webhook settings. Clicks first, then the move from sandbox to live, which is where most integrations break.

The three places you need

Client ID and Secret: log in, open Apps & Credentials, check the toggle at the top says Sandbox or Live, then open your app (or the Default Application) and copy both. Use Create App for a separate project.

Log in to Dashboard Apps & Credentials Your app

Test buyer and seller logins: Testing Tools, then Sandbox Accounts. You start with one personal and one business account. Use the ⋮ menu and View/Edit Account to see the email and password, and sign in with them at sandbox.paypal.com.

Testing Tools Sandbox Accounts ⋮ View/Edit Account

Webhooks: inside the app's settings, add a webhook URL and pick the events to send. Each app takes up to 10 webhook URLs.

From a sandbox app to a live one

  1. 1

    Create the sandbox app

    Apps & Credentials Sandbox Create App

    Name it after the site or system that will use it, choose the merchant type, and link it to the default sandbox business account. You get a sandbox Client ID and Secret straight away.

  2. 2

    Turn on the features you need before getting a token

    The app's settings have a Features list, for things like Payouts. Switch on what you'll use first.

    Watch for: Tokens issued before you changed a feature keep their old permissions until they expire. Request a fresh token after a change.

  3. 3

    Get an access token

    Post your Client ID and Secret as basic auth to /v1/oauth2/token with grant_type=client_credentials. The response has an access token and an expires_in in seconds. Send the token as a Bearer header, and request a new one before it runs out rather than on every call.

  4. 4

    Run full payments with the sandbox accounts

    Use the Orders API to create an order, approve it as the sandbox personal account, then capture it. Check the money landed in the sandbox business account. Test a refund and a declined approval too.

  5. 5

    Subscribe a webhook and test it

    Add your endpoint in the app's webhook settings. PayPal's webhook simulator can send sample events while you build.

    Watch for: Simulated events can't be checked with PayPal's verify-signature endpoint. Test real verification with real sandbox payments.

  6. 6

    Switch the toggle to Live and set it up again

    Apps & Credentials Live Create App

    Live needs a PayPal business account. Live apps get their own Client ID, Secret and webhook ID, and calls go to the live API host instead of api-m.sandbox.paypal.com.

It worked in sandbox and fails in live

Sandbox credentials pointed at live, or the other way round

How you'll know: invalid_client or authentication errors straight after the switch.

Fix: Sandbox and live credentials are entirely separate, and each only works against its own host. Store them per environment and pick both from one setting.

Webhook signature checks fail in production

How you'll know: Every live event is rejected by your own verification code.

Fix: The webhook ID used in verification is still the sandbox one. Each app has its own webhook ID. Swap in the live app's ID.

Duplicate orders or refunds

How you'll know: One payment shows twice in your system, usually after an outage or a slow response.

Fix: PayPal resends an event whenever your endpoint doesn't reply with a 2xx, up to 25 times over three days. Reply quickly, then record each event ID and skip ones you've already processed.

Payouts calls refused in live

How you'll know: Payouts worked in sandbox, and live returns a permission error.

Fix: Live Payouts needs PayPal to grant access to the business account first. Apply early; you can keep building in sandbox while you wait.

What the main PayPal APIs do

The dashboard gives you credentials. These are what you call with them.

01

Orders

Create an order, let the buyer approve it, then capture the payment. The core of a custom checkout.

02

Payments: refunds

Refund a capture in full or in part. How the refund itself reaches the buyer is on PayPal refunds.

03

Payouts

Send money to many people in one batch: affiliates, sellers, contractors. Each item in a batch can succeed or fail on its own.

04

Webhooks

PayPal pushes events such as a completed capture, a refund or a new dispute to your URL, so you don't poll. Disputes tie into PayPal buyer protection.

Once it is live: the jobs nobody wrote into the ticket

A working capture is the start. Somebody has to decide what happens after it: the order released to fulfillment, stock taken down, the sale and its fee booked in the accounting system. The official WooCommerce, Shopify and WordPress plugins handle the payment screen well, and stop there. PayPal fees and PayPal to QuickBooks cover what that booking looks like.

Payouts need the same care. The batch call sends the money, but your own system has to know who's already been paid this cycle, retry the one recipient that failed while the rest succeeded, and tell finance it happened.

n-frames builds that layer on the PayPal API: webhook handlers that verify every event and process it once, payout runs that log each result back to the system that tracks who's owed, and the handoff from a captured payment to fulfillment and your books.

Questions people ask

What do I need to start building with the PayPal API?

A login to the PayPal Developer Dashboard at developer.paypal.com (your regular PayPal login works) and an app under Apps & Credentials. That gives you a sandbox Client ID and Secret to build against. Live credentials come later and need a PayPal business account.

What's the difference between PayPal sandbox and live credentials?

Sandbox credentials work against test accounts and fake money on the sandbox host. Live credentials move real money on the live host. Your request code is the same, but the credentials, the host and the webhook ID all change, and none of them work in the other environment.

What is the PayPal Payouts API used for, and who can turn it on?

Paying many recipients in one batch call, such as marketplace sellers, affiliates or contractors on the same schedule. For live use, PayPal has to approve Payouts on your business account first.

How do PayPal webhooks work?

You add an endpoint URL to your app in the developer dashboard and choose events. PayPal posts each event there (a capture completing, a refund, a dispute opening) and retries if you don't answer with a 2xx. Verify each one, either with PayPal's verify-signature endpoint or by checking the signature yourself.

Do I need a developer to integrate PayPal into my website?

Not for a standard checkout button or the official WooCommerce or Shopify plugin; those only need the Client ID and Secret from the dashboard. You need one for direct API work: custom checkouts, webhooks, Payouts, or connecting payments to inventory, fulfillment and your books.

Can the PayPal API automate refunds?

Yes. A captured payment can be refunded through the API in full or in part, and PayPal sends a webhook when it completes, so your order and accounting records can update. How the refund itself reaches the buyer, and when, is on our PayPal refunds page.

Where are webhook event logs in the PayPal developer dashboard?

The dashboard keeps a record of webhook events per environment, and a delivery that failed for three days can be resent by hand from there. Look for webhook events in the dashboard's left-hand navigation, with the toggle set to the environment you're checking.

Who builds custom PayPal API integrations?

n-frames does. We build PayPal checkouts, webhook handlers, payout runs and the connections from PayPal to your order, inventory and accounting systems, and keep them running after launch.

Keep reading

PayPal Business Account How to open or upgrade to a PayPal business account, what it costs, how it differs from personal, and why your PayPal transfers never match your sales.PayPal Fees PayPal's US fees by payment type, what friends and family payments cost, the extra charges for disputes and instant transfers, and a worked example.PayPal Refund How long a PayPal refund takes to reach you, why it says pending, what to do if the seller won't refund, and how sellers issue one.PayPal Seller Protection What PayPal Seller Protection covers (unauthorized payments, items not received), what it doesn't, the proof of delivery PayPal wants, and Buyer Protection.PayPal Invoice How to pay a PayPal invoice, how to spot a fake one, and how to send your own: the steps, the fee, recurring invoices, and what happens after payment.Reconcile PayPal in QuickBooks to the Statement Reconcile PayPal in QuickBooks like a bank account, against PayPal's monthly statement, and find the fee, reversal or opening balance that keeps it off.Stripe API Where the Stripe API keys are, the order to build a first payment in, the production bugs test mode never shows, and how to get fees and payouts back out.Stripe Webhook Setup Set up a Stripe webhook endpoint in Workbench, find the signing secret, pick the right event for each job, and fix deliveries that show Failed.Stripe vs PayPal Stripe vs PayPal on US list rates, checkout control, subscriptions and buyer trust, a worked $80 order on each, and what changes once you run both.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.