Skip to content
Oct 28, 2026 6 min read

With PayPal, the buyer pays on the PayPal page and comes back to your store or, if you choose so, types the card in your own store. To connect it you create an app in PayPal’s developer dashboard, paste its keys in your panel and add a webhook.

1. The app and its keys

  1. Sign in at developer.paypal.com with your PayPal account and open Apps & Credentials.
  2. PayPal has two environments with different keys: Sandbox (testing) and Live (real). Pick one on that same screen. Start with Sandbox.
  3. Under REST API apps there is an app called Default Application; for one of your own, click Create App.
  4. Open the app and copy the Client ID and the Client secret.
  5. In the panel, open Payment methods, choose Paypal in Select Method and paste them: the Client ID in “Client key” and the Client secret in “Secret key”. Sandbox ones go in the “(test)” fields; Live ones, in the others.
  6. Leave Environment on Development (it uses the “(test)” fields, that is, Sandbox), save and make a test purchase with a Sandbox test buyer account.
  7. When it works, repeat steps 2 to 5 with Live, switch Environment to Production and save.

The panel does not show the secret key again once saved: the field comes back empty and, if you leave it empty when saving, the one you had is kept.

Where the customer pays

In the PayPal section, among the technical options, Where the customer pays has two options:

  • On the payment page of the gateway (recommended), the default: the customer clicks Pay … with PayPal (with the amount), pays on the PayPal page with their account or a card and comes back to your store.
  • Card form on your shop page: the customer types the card without leaving your store, in fields provided by PayPal, and if their bank asks for it they confirm the payment in a bank window (3-D Secure). Below, they still have the Pay with my PayPal account instead link.

PayPal has to approve the card form on your account. PayPal calls it Advanced Credit and Debit Card Payments and approves it account by account: only for business accounts and in the countries it supports (Spain among them), and it may refuse it. In Sandbox it usually comes turned on; in Live, open your app in Apps & Credentials and check that it shows and is ticked. Until PayPal approves it, or if it refuses, you do not have to do anything: your store detects it on every purchase and takes the customer to the PayPal page, as with the other option.

To test it, leave Environment on Development and pay with PayPal’s test cards (test card generator; for 3-D Secure, the ones in its 3-D Secure testing guide).

Either way the same amount is charged, the order is closed the same way and the webhook works for both. With the form on your page the card details go straight to PayPal, but the page that collects them is yours: if your bank or PayPal ask you for the card security questionnaire (PCI DSS), it is SAQ A-EP, not the SAQ A of the redirect.

The name and logo the customer sees

On the PayPal page the customer sees the name of your store: edeck.me sends PayPal your site’s title with every purchase. That name replaces the one of your PayPal account on that page.

The logo is not sent by your store: there is no field in the panel to upload it. PayPal manages it from your account: in PayPal’s official documentation, the logo and the company name are changed in the account settings (the business profile of your business account). Note: the PayPal documentation we checked does not confirm that the account logo appears on the payment page of this integration; if you do not see it there, that is a PayPal limitation, not your store’s.

2. The webhook

Without a webhook, a payment that PayPal leaves under review is only closed if the buyer comes back to your store, and refunds, reversals or disputes (chargebacks) do not reach the order. With it, PayPal tells your store; if a buyer opens a dispute, the order says so in red so you do not ship it, and if you lose it, it counts as refunded. The PayPal section of the panel shows your store’s address (it ends with your site number): that is the one to paste in PayPal, and it is different for every store.

  1. In PayPal Developer, open Apps & Credentials in the same environment (Sandbox or Live) and open your app.
  2. Find the app’s webhooks and click Add Webhook.
  3. As the webhook address, paste the one the panel shows.
  4. Select the five payment capture events: PAYMENT.CAPTURE.COMPLETED, PAYMENT.CAPTURE.DECLINED, PAYMENT.CAPTURE.DENIED, PAYMENT.CAPTURE.REFUNDED and PAYMENT.CAPTURE.REVERSED; and the three dispute events: CUSTOMER.DISPUTE.CREATED, CUSTOMER.DISPUTE.UPDATED and CUSTOMER.DISPUTE.RESOLVED. Save.
  5. PayPal assigns it a Webhook ID (letters and numbers, no spaces). Copy it and paste it in the panel: in “Webhook ID (test)” if you created it in Sandbox, or in “Webhook ID” if you created it in Live. Save.

The Sandbox webhook and the Live webhook are different: you have to add each one in its own environment. Your store has to answer PayPal over HTTPS, which edeck.me addresses already do.

If PayPal says a notification could not be delivered, check the webhook’s events in its developer dashboard and that the Webhook ID pasted in your panel is that webhook’s.

PayPal’s menu names can change; if you do not see exactly those texts, look for the part of your app where its webhooks are managed.

Can’t find it? Write to us at soporte@edeck.me and tell us which screen and which site. We reply within one working day.

← Back to the help center

Was this guide helpful?

No website yet? We will propose one on edeck.me: 30 days free with a card, from €4.99/month.