Pipedream components for U.CASH Pay: create crypto + card checkouts and receive verified settlement webhooks. Non-custodial.
- Action - Create U.CASH Pay Checkout (
components/ucash-pay/actions/create-checkout.cjs): creates a hosted checkout and returns thepayment_url+transaction_id. Exports both for downstream steps. - Source - New Verified Webhook (
components/ucash-pay/sources/new-webhook.cjs): an HTTP endpoint that receives U.CASH Pay webhooks, verifies theX-Webhook-Signature(HMAC-SHA256 overt.raw_body, 300s replay window), and emits the event.
- Sign up at pay.u.cash with email + password, then click the verification link in the email.
- Set your receive addresses under Settings → Addresses (a wallet per coin, or ENS/Unstoppable/FIO names). Crypto settles here.
- Create a store at Account → Stores → + Add Store.
- Copy the store credentials: the Store Cloud Token (for the action) and the Store Webhook Secret (for the source). Use the store-level token, not the account-wide one.
- Set the webhook URL: deploy the New Verified Webhook source, copy its endpoint URL, paste it into the store's Store Webhook URL field in pay.u.cash, save, then Test Webhook.
In Pipedream, paste the Store Cloud Token into the action's secret prop, and the Store Webhook Secret into the source's secret prop.
In Pipedream you can use these as custom components: copy the .cjs files into your Pipedream account (Sources/Actions → New → custom component), or publish them to the Pipedream components registry and reference the app. See the Pipedream custom components docs.
The signature is HMAC over the raw request body. Pipedream exposes the raw body as a string when the request isn't parsed as JSON; if Pipedream parses the body into an object first, the source falls back to event.bodyRaw, or re-serializes the parsed object. If signature verification fails in your account, ensure the webhook delivers the raw body (or adjust the source to use Pipedream's raw-body accessor for your runtime version).
MIT.