How I would run support and payments operations for Ethena Pay from the first ticket, and a working desk built on Ethena Pay's published pages and the Avalanche chain.
Five weeks after launch, the loudest public questions are about access: waitlist position, codes, Android, country. Behind them sit the money tickets: card, disputes, deposits, KYC, recovery.
Answer those well from day one, put every money exception under a runbook with a second reviewer, and remove the top clusters with product fixes so contacts per user fall as users grow.
A desk that reads the live public queue (X replies, App Store reviews in 48 storefronts), triages a ticket in five languages, routes it to Rain, Sumsub, Privy or Iron/MoonPay, reads Avalanche live, holds money replies for four-eyes, runs the dispute and complaint clocks, and shows the weekly read.
| Takeaway | Why it matters |
|---|---|
| The support inbox is also the card servicer | Card Terms and the Complaint Procedure route issuer servicing and complaints to support@ethenapay.co and 1-844-ETHA-PAY. Card disputes start in this queue. |
| Self-custody changes the hard tickets | Ethena Pay cannot see keys or reverse onchain transfers. Recovery, wrong-network sends and scams need clear, honest scripts and fast prevention. |
| The bar is reachable | Crypto cards cluster between 2.3 and 3.4 on Trustpilot. Revolut sits at 4.7 with AI-first chat and a clear route to a human. That design, applied to a crypto card, is the target. |
| Access is a product question | About 10% of the waitlist was onboarded by 3 October. In-app status and a published mechanism remove most of those contacts before they start. |
A self-custodial stablecoin money app on Avalanche, with a Visa card, live on iOS since 1 September 2026. Each feature adds a class of ticket.
| Area | What is public | Support read |
|---|---|---|
| Operator | Ethena Pay Ltd, Malta (C 114576), a software and technology provider. Regulated services sit with third-party providers. | Replies must name who does what without over-promising. |
| Reach | Live in 48 countries across Latin America, the Caribbean, Asia and the Middle East, Africa and Oceania. US, EU, UK, Switzerland, Canada, Taiwan and South Korea "live soon". iOS only; Android "coming soon". | Spanish and Portuguese for 17 LatAm markets; time zones from UTC-6 to UTC+12. |
| Traction | 400 early-access users at launch; 1,600 users and $1.5M moved by 25 September; about 10% of the waitlist onboarded by 3 October. | The waitlist is the larger audience today. |
| Card | Virtual Visa, Apple Pay (Google Pay "available soon"), secured by collateral in the user's wallet, 0% APR. No Ethena FX fee; the network fee (around 1%) passes through. ATM $1.00 + 0.65%. Late fee up to $40. | Declines, provisioning, collateral and fee questions. |
| Rewards | Cashback 4% to 5% by tier in banded steps, paid daily in AVAX after settlement. Daily Boost to a 5% or 6% total rate on capped balances, needing one card transaction a month. $30 referral in AVAX. | "Why less than 4%" and "where is my cashback" are pre-answered in the FAQ, which signals volume. |
| Support today | Email with a 24 to 48 hour target, a toll-free number, in-app help, @EthenaPay on X. Complaints acknowledged in 5 business days, final response aimed at 15, no later than 35. | No public help centre or status page yet. |
Sources: FAQ · Pricing · Jurisdictions · Support · Complaints · @EthenaPay, 25 Sep
The JD makes the CSM the named operational owner of these vendors. Each row is a different escalation path.
| Vendor | Role (from the Terms) | Tickets it drives | Escalation needs |
|---|---|---|---|
| Rain / Third National | Program manager and Visa issuer for the secured card; Puerto Rico law; 60-day dispute window from statement posting. | Declines, Apple Pay, disputes, statements, late fees. | Auth ID, decline code, statement line. |
| Sumsub | Identity verification, sanctions screening, liveness, fraud screening. | Rejected documents by nationality, retries, one-account rule. | Applicant ID, rejection label. |
| Privy | Login and embedded self-custodial wallet. | Lost phone, passkeys, recovery. | Login method, device change date. |
| Iron / MoonPay | On and off-ramp, virtual IBAN, bank transfers. | Deposits not arrived, IBAN by country. | Partner reference, rail, send time. |
| Avalanche | Settlement of USDe balances; AVAX cashback. | "Sent but not showing", wrong network. | Tx hash, token, recipient. |
Sources: Terms of Use §1.5, §5.4 · Spend Card Terms. Plasma One, ether.fi Cash and KAST also card on Rain, so the card pipeline is shared across peers; triage speed and clarity are where Ethena Pay can differ.
Clustered from public replies to @EthenaPay and App Store reviews since launch, plus the FAQ's own pre-answered questions. The demo's live tab re-reads this queue: on 5 October, 90 questions sat under 8 recent @EthenaPay posts, 37 of them about country or Android availability. Money = a second reviewer before any credit, reversal or filing.
| Cluster | Public signal | Money | Best removal |
|---|---|---|---|
| Waitlist and access codes | Positions reported moving backwards; promised codes; "wait for 2000 people" (App Store). | No | In-app status with the batch mechanism; log position regressions as defects. |
| Country and Android | The most repeated request, in English, Chinese, Korean, Spanish. | No | One help-centre page and launch announcements; no dates promised. |
| Support reach | Users told to DM while DMs were reported closed; long email waits. | No | One in-app route with a visible reference and next-update time. |
| Card provisioning | "Can't get my card at Apple wallet"; KYC done, no virtual card. | No | Pre-flight check before Apple Pay add, with a specific error. |
| KYC documents | Passports from some countries not accepted. | No | Document guidance by nationality before upload. |
| Tiers and referrals | How to move past Standard; missing referral codes. | Small | Publish tier rules where users look. |
| Cashback and Boost | Banded rates, AVAX value, settlement delay. | Yes | Pending cashback per purchase, with its date. |
| Recovery | "Where can I get my backup seed phrase?" | Funds at risk | Recovery set-up prompt at onboarding. |
| Disputes, deposits, collateral | Low public volume so far; grows with spend. | Yes | Runbooks with four-eyes (§07). |
The JD says few competitors set a high bar. The public record agrees: the same three complaints repeat across crypto cards.
| Product | Model | Trustpilot | Support model | Recurring complaint |
|---|---|---|---|---|
| Ethena Pay | Self-custody, USDe balance, Rain/Visa card, AVAX cashback. | No page yet | Email 24-48h, phone, in-app, X. | Waitlist, reply speed. |
| Plasma One | Self-custody stablecoin card on Rain; 180+ countries. | 3.1 (5) | "24/7", AI plus human. | KYC rejection, template replies. |
| ether.fi Cash | Non-custodial card on Rain; yield on collateral. | 3.9 (89) | Discord, member priority. | Deposit locks, referral changes. |
| KAST | Custodial stablecoin card; 170+ countries. | 2.5 (215) | In-app, Telegram, Discord. | Frozen accounts, SEPA stuck. |
| RedotPay | Custodial crypto card; 130+ countries. | 3.0 (958) | Live chat, help centre, Telegram bot. | 2 to 3 day replies, withheld funds. |
| Bleap | MPC self-custody, Mastercard; moving into Mexico and Brazil. | 3.3 (67) | In-app only. | Replies taking weeks. |
| Gnosis Pay | Safe self-custody card; consumer card closing 20 Dec 2026. | 2.3 (38) | Help centre. | Blocked funds. |
| Crypto.com | Exchange with card, large reach. | 1.9 (9,456) | 24/7 chat, bot first. | AI question loops. |
| Revolut | Licensed neobank with crypto. | 4.7 (468,796) | AI chat with a clear route to a human. | Benchmark. |
Trustpilot scores and review counts read 5 October 2026. Mantle's UR (pays on USDe) and Bitget Wallet Card are close substitutes in Asia and LatAm. Model and support columns from each product's public pages.
Encoding the FAQ, Pricing and Terms into macros meant reading them side by side. The pages are thorough and clearly written; three small wording items would help an agent who has to pick one answer. The demo re-checks each live.
| Item | What the pages say | Suggested fix |
|---|---|---|
| Cashback minimum | FAQ: "Transactions under $1.00 do not earn cashback." Pricing: "Transactions of $1.00 or less do not earn cashback." Pricing settles the exactly-$1.00 case; the FAQ leaves it open. | Align the FAQ to Pricing, which calls itself the authoritative source. |
| Country list | The jurisdictions page lists Antigua and Barbuda among the 48 live countries; the Terms Appendix 1 country sections do not include it. The "live soon" lists also differ (UK and Switzerland on one, China on the other). | Sync the two lists, or link the Terms list to the jurisdictions page. |
| Gas fees by chain | Pricing's gas row covers "transfers on the Supported Blockchains (Ethereum, Polygon, Optimism, Arbitrum)". Transfers in the app run on Avalanche, which the Disclaimers include. The Card Terms definition may be scoped to card collateral on purpose. | Name Avalanche in the Pricing gas row, so the fee answer for an in-app transfer is on the page. |
Checked 5 October 2026 against FAQ, Pricing, Jurisdictions, Terms, Card Terms. Live status in the demo's Doc sync tab.
| JD duty | How I would do it | Detailed in |
|---|---|---|
| Own the queue and Zendesk end to end | Work most tickets myself from week one. Tags = the clusters in §03; one macro per cluster, sourced to a page; publish first-response and resolution targets and report against them weekly. | §06, demo 1 |
| A quality bar users talk about | Written standard, weekly QA sample with critical items (secrets, guarantees, tipping-off), CSAT per cluster, public sentiment tracked on X and the App Store, and outreach to affected users before they write in. | §06 |
| Support as measured input to product and engineering | Monday read: contacts per 100 actives by cluster, change, top defects with impact and owner. Paging thresholds for emergencies; everything else waits for the read. | §08, demo 4 |
| Automate the work | Fix the cause of the largest clusters, ship self-serve answers and automated status, AI triage and drafting with a human check where money is involved. Agent minutes per active user as the tracked goal. | §08, demo 1 |
| Named owner of the rails vendors | Escalation path and contact per vendor, a vendor incident log with users affected and time to fix, and that evidence brought to commercial reviews. | §02, demo 6 |
| Manual money workflows under control | Runbook, four-eyes and audit trail for reconciliation, disputes, refunds, stuck withdrawals, fraud and KYC edge cases, agreed with Finance and Compliance. | §07, demo 1, 3 |
| Build and lead the function | One operation across Zendesk, Telegram and X; user-facing incident comms; a KPI dashboard; then the first hires toward follow-the-sun and Spanish, Portuguese and Chinese cover. | §09 |
Targets I would propose to publish, measured from day one. Starting points to agree with the team, then tightened as volume settles.
| Measure | Target | How |
|---|---|---|
| First response, money and security | 1 to 4 hours | Priority by cluster at intake; fraud and takeover at P1 any hour. |
| First response, everything else | Under 24 hours | Inside today's public 24 to 48 hour promise, then tightened. |
| Every reply | Says what happened, what we did, when they hear next | QA critical item; the demo blocks a reply with unfilled fields. |
| CSAT | Measured per cluster | One-tap survey on solve; low scores reviewed weekly. |
| Public sentiment | Weekly count of unanswered public questions | @EthenaPay replies, App Store reviews per storefront, Telegram and Discord. |
| Proactive contact | Affected users told before they ask | Incident banner, X post and a follow-up email to the users affected. |
| Never | Ask for a seed phrase, passkey, code or PIN | QA block; repeated in every security reply. |
One runbook per exception, a second reviewer for any money action, and an audit entry for every step.
| Workflow | Runbook core | Four-eyes on | Clock |
|---|---|---|---|
| Card dispute | Authorised vs settled, merchant first, evidence, file with Rain, explain cashback reversal. | Amount, reason, window. | 60 days from statement posting. |
| Refund | Match the refund to the charge; band released; cashback reversed. | Any manual credit. | Settlement, usually 1 to 3 business days. |
| Stuck deposit or withdrawal | Fiat leg (Iron/MoonPay) or onchain leg (Avalanche); confirm network, token, recipient. | Manual credit or reversal. | Partner SLA, then daily update. |
| Fraud and takeover | Freeze first, verify in-app, device history, issuer fraud case. | Re-issue, refund, account change. | P1, any hour. |
| KYC edge case | Retryable vs final; nationality coverage; screening reasons stay with Compliance. | Any override request. | Sumsub review time. |
| Reconciliation break | Ledger vs issuer settlement vs chain; daily diff; owner per break. | Every adjusting entry. | Same day. |
| Complaint | Register on receipt, route to Compliance or Legal. | Final response. | 5, 15 and 35 business days. |
The goal is fewer contacts per user each month. Each fix below targets one cluster, has an owner, and gets a before-and-after rate once it ships.
| Fix | Cluster removed | Owner | Measured by |
|---|---|---|---|
| In-app waitlist status, with how batches open | Waitlist and codes | Product, design | Waitlist contacts per 100 waitlisters. |
| Help centre on Zendesk, starting with countries, Android, tiers | Availability, tiers | Support | Deflection rate; article views per contact. |
| Apple Pay pre-flight check with a specific error | Card provisioning | iOS, Rain | Provisioning contacts per new card. |
| Document guidance by nationality before upload | KYC | Product, Sumsub | First-pass KYC rate. |
| Pending cashback per purchase, with its date | Cashback | Product, design | Cashback contacts per 100 cardholders. |
| Automated deposit status: confirmations and partner ETA | Deposits | Eng, Iron/MoonPay | Deposit contacts per 100 deposits. |
The demo's Weekly read tab models these fixes on a synthetic month so the trade-offs are visible; real numbers replace the assumptions within the first weeks.
Grow capacity only where the data says the queue needs it, in the order users need it.
| Piece | What it looks like | Trigger |
|---|---|---|
| One operation | Zendesk as the system of record; Telegram, X and email land as tickets with one reference per user. | Month 1. |
| Incident comms | In-app banner, @EthenaPay post, proactive email, named update times; templates ready per vendor. | Month 1. |
| KPI dashboard | Contacts per 100 actives, response and resolution vs target, CSAT, agent minutes per user, vendor incidents. | Month 1, weekly after. |
| Spanish and Portuguese cover | 17 LatAm markets; outsourced or contracted front line with my QA. | LatAm share of contacts. |
| Follow-the-sun | Asia-Pacific, Europe and Americas shifts for P1 and money tickets. | P1 volume outside covered hours. |
| Payments ops | A specialist for disputes, reconciliation and vendor cases. | Dispute and break volume after the card scales. |
Built from the public job posting (2026), Ethena Pay's public pages, App Store listing, public posts on X and Trustpilot, read on 5 October 2026. The demo is my own tool, built for this application; its tickets, metrics and names are synthetic, its facts are re-read from pay.ethena.fi, and its chain data comes from the public Avalanche RPC. Unsolicited interview homework; happy to walk through any section.
Product: FAQ · Pricing · Promotions · launch post
Legal: Terms of Use · Spend Card Terms · Complaint Procedure
Reach: Jurisdictions · Support · App Store
Public posts: launch · 1,600 users · @EthenaPay
Peers: KAST · RedotPay · Revolut · Plasma One
Independent homework for the Ethena Pay Customer Success Manager role · 2026 · edwardtay.com