PayPal
Create and manage PayPal orders, payments, invoices and payouts.
About
PayPal ships in the w6w first-party pack. It declares 13 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.paypal- Version
- 0.2.1
- Author
- w6w
- Licence
- MIT
- Categories
- Commerce & Payments · Finance & Accounting
Overview
PayPal creates and manages orders, payments, invoices and payouts through PayPal’s own REST API, working against either a live or sandbox app depending on the credentials connected. Orders can be created and captured, a completed capture can be looked up and refunded, and invoices can be created, listed, read and sent to a customer.
Payouts to one or many recipients can be created, checked and cancelled, accepting PayPal’s own payout-item shape directly so a multi-recipient batch doesn’t need to be flattened into a simplified form first. Capture and refund actions carry PayPal’s own idempotency key so a retried step can’t double-charge or double-refund a customer, and a retried payout batch is deduplicated the same way through its own batch id.
Authentication is app-level rather than tied to any individual buyer, using PayPal’s client-credentials grant — the same shape suited to scheduled and unattended workflow runs, with no browser sign-in step involved.
Build with PayPal
Three routes to the same 13 actions. The Workflow tab is generated from PayPal's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Cancel a payout item
payout-item-cancel Cancel an unclaimed payout item and return its funds to the sender.
List transactions
transaction-list List transactions in a date range, from the Transaction Search API.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying PayPal's real ids.
{
"manifestVersion": "2",
"name": "paypal-example",
"steps": [
{
"id": "invoice-create",
"uses": {
"app": "io.w6w.paypal",
"action": "invoice-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"recipientEmail": "<recipientEmail>"
}
}
]
}Here are some of the things you can do
-
Create a draft invoice
performinvoice-create -
Get an invoice
readinvoice-get -
List invoices
searchinvoice-list -
Send an invoice
performinvoice-send -
Capture an order
performorder-capture
+8 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for PayPal, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to PayPal. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "order-create",
payload: {
intent: "<value>",
// amount: "<value>",
// description: "<value>",
// additionalOptions: "<value>",
// additionalFields: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action order-create --payload '{"intent":"<value>"}'Give an AI agent PayPal — without giving it PayPal's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.paypal#invoice-create",
"input": {
"recipientEmail": "<recipientEmail>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's PayPal connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
PayPal's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. PayPal itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
PayPal declares its own checks, so its health is a property of the app rather than something the host guesses at.
PayPal platform status
PayPal's status feed (paypal-status.com), read for open (non-Resolved) incidents. Unauthenticated and unsigned.