Skip to content

PayPal MCP

PayPal MCP is a component that lets you connect your Nappai dashboard to PayPal.
It lets you choose a PayPal tool (like creating a payment or checking a transaction) and run it with your own API key and environment (sandbox or live).

How it Works

PayPal MCP uses the PayPal API to perform actions.
When you add the component, you provide your PayPal API key (the access token) and pick whether you want to work in the sandbox (testing) or live (real money) environment.
The component automatically finds all the PayPal tools that are available in the PayPal API and shows them in the Tool dropdown.
When you run the component, it sends a request to PayPal with the chosen tool and the data you supply, then returns the response from PayPal.

Inputs

  • API Key: Your PayPal API key (access token). This is required to authenticate with PayPal.
  • Tool: Select the PayPal tool you want to run, such as “Create Payment”, “Get Transaction Details”, or “Refund Payment”.
  • Environment: Choose “sandbox” for testing or “live” for real transactions.

Outputs

The component returns the raw response from PayPal for the selected tool.
The output is usually a JSON object that contains the result of the API call, such as payment status, transaction ID, or error messages.
You can use this output in later components to make decisions, store data, or display information to users.

Usage Example

  1. Add the PayPal MCP component to your workflow.
  2. Enter your API Key (keep it secret).
  3. Select “sandbox” as the environment to test.
  4. Choose “Create Payment” from the Tool dropdown.
  5. Connect the required payment details (amount, currency, payer info) from previous components.
  6. Run the workflow.
  7. The component will return a JSON response that includes the payment ID and status, which you can then pass to a “Store Payment” component or display to the user.
  • PayPal Payment – A simpler component that only creates payments.
  • PayPal Refund – Handles refunding a payment.
  • PayPal Transaction Search – Looks up transaction details by ID.

Tips and Best Practices

  • Use the sandbox environment first to test your workflows without spending real money.
  • Keep your API Key secure; store it in Nappai’s secret manager instead of hard‑coding it.
  • Verify the Tool you select matches the data you provide; mismatched inputs can cause errors.
  • Check the output for error codes and handle them gracefully in your workflow.

Security Considerations

  • The API Key is a secret credential; never expose it in logs or public outputs.
  • Use Nappai’s secret storage to keep the key safe.
  • When moving to the live environment, double‑check that the key has the correct permissions and that you’re not accidentally processing real payments during testing.