القائمة
Take payments via Stripe — one-off or recurring. Connect your own Stripe account, then create hosted Stripe Checkout URLs. No raw card data ever touches your code.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | my-payments-api |
| version | 1.1.0 |
| description | Take payments via Stripe — one-off or recurring. Connect your own Stripe account, then create hosted Stripe Checkout URLs. No raw card data ever touches your code. |
| triggers | ["payment","stripe","checkout","charge","subscription","take payments","billing","refund","recurring","sell"] |
| checksum | sha256-pending |
Wraps Stripe. Agents create Checkout URLs, paste them into the frontend, customers pay on Stripe-hosted pages. MyAPI never custodies funds — Stripe is the merchant of record on your connected account.
Bring your own Stripe (T0). myapi payments connect --stripe-key <sk_...> links your existing Stripe account with your own secret key. The key is validated live against Stripe, stored encrypted, and never echoed. Your Stripe account stays the merchant of record. (Connect Express / MyAPI-onboarded accounts — "T1" — are not yet available; the backend returns 501 T1_DEFERRED.)
One verb covers one-off and recurring. myapi payments charge --amount 9.99 creates a one-off Checkout URL. Add --every month (or --every year) and the same verb creates a subscription Checkout URL instead. No separate subscribe verb. --amount is in dollars (e.g. 19 or 9.99) and must be positive.
Charge returns a hosted Stripe Checkout URL. The agent sends the customer to that checkout_url — paste it into a frontend, an email, or a redirect. The card-entry surface is owned entirely by Stripe Checkout (SAQ-A scope only); MyAPI infra never touches raw card data.
Optional charge fields: --description <text> (line-item label), --email <addr> (pre-fill the customer's email), --success-url <url> / --cancel-url <url> (where Checkout redirects after the session).
Refunds are full only. myapi payments refund <charge_id> issues a full refund. Partial refunds are not supported.
| Command | What it does |
|---|---|
myapi payments connect --stripe-key <sk_...> | Link your own Stripe account (T0 — bring your own key) |
myapi payments status | Show the org's Stripe connection status |
| `myapi payments charge --amount [--every month | year] [--description |
myapi payments list | List charges in your org |
myapi payments get <charge_id> | Inspect a charge |
myapi payments refund <charge_id> | Full refund (no partial) |
# ── Setup: connect your Stripe account (T0 — bring your own key) ─────────────
myapi payments connect --stripe-key sk_live_abcd1234...
# → Stripe connected. Your existing Stripe account stays the merchant of record.
myapi payments status
# → Tier / Stripe account / onboarding status
# ── Take a one-off payment ──────────────────────────────────────────────────
myapi payments charge \
--amount 9.99 \
--description "Pro plan upgrade" \
--email customer@example.com
# → Charge created: pay_... — returns a hosted Stripe Checkout URL.
# Send the customer to that checkout_url (frontend, email, redirect).
# ── Take a recurring payment (subscription) ────────────────────────────────
myapi payments charge \
--amount 29 --every month \
--description "Pro plan" \
--success-url https://acme.com/thanks \
--cancel-url https://acme.com/pricing
# ── Lifecycle ───────────────────────────────────────────────────────────────
myapi payments list
myapi payments get <charge_id>
myapi payments refund <charge_id>
connect only accepts your own sk_... key today; T1 returns 501 T1_DEFERRED.--amount inline on each charge.my-crm-api has the engagement view).Run myapi payments --help or myapi payments <subcommand> --help for full flag reference.
Deploy JavaScript functions to the MyAPI edge runtime (Cloudflare Workers). Register a function, upload a single-file JS bundle, get a live HTTP invocation URL or run it on a cron schedule. Each function gets a scoped capability key for cross-slot calls.
Tracking pixel + identity resolution for MyAPI funnels and email. Capture visits and events, resolve known users to anonymous sessions, stream interaction events for analytics. Pairs with mycrmapi for auto-ingest of pixel_visit events on known contacts.
Auth, organizations, and billing hub. Start here to get an api_key and org_id — every other service depends on both.
Saved audiences = named Goldfox-filter snapshots over the people or company database. Build a target list once, name it, reuse it across campaigns, refresh to re-evaluate against current data. The persistence layer on top of my-people-api + my-company-api.
Register new domains and manage edge settings. Required before a funnel can go live on a custom URL.
Synchronous single-address email verification — syntax + DNS + Microsoft GetCredentialType probe. Returns a verdict in <1s for ~50% of inputs; the rest get verdict='unknown' with smtp_recommended=true. The pre-send quality gate for any outbound campaign.