Payments with Stripe: What It Unlocks (SDR Version)
Why Stripe matters in Ribbn (SDR framing)
Stripe is the payment rail that lets Ribbn merchants take card payments and manage payment methods/payout destinations—without Ribbn becoming a bank or “money movement” product. In SDR terms: Stripe unlocks secure payments while Ribbn stays the operational system of record for secondhand workflows (inventory lifecycle + webshop + POS + seller attribution/payout readiness).
Use this page to:
- Answer “Do you support payments?” and “What do we need to start?”
- Set correct expectations on what is configured in Stripe vs. Ribbn
- Handle the most common gotcha: refunds are not done inside Ribbn
Scope guardrails (SDR): Keep it to documented product behavior and workflows. Do not give tax/VAT or financial advice. Avoid committing to specific payment methods or payout timelines beyond what Ribbn explicitly supports.
What connecting Stripe unlocks (the promise you can safely make)
When a merchant connects Stripe from Ribbn, they unlock:
- Payments acceptance after Stripe setup is completed (integration becomes active).
- Configurable payment methods offered at checkout (selected in Stripe onboarding).
- A payout destination (bank account configured in Stripe).
- A consistent way to manage the connection later via Ribbn → Payments → Go to Stripe Account.
Key limitation to state early: **Ribbn does not process customer refunds inside Ribbn when using Stripe**. Refunds must be issued **manually in Stripe**.
Prerequisites (what to check before you pitch “easy to turn on”)
Before a prospect can connect Stripe, they need:
- Access to Ribbn Admin Dashboard
- Business and banking information required by Stripe onboarding (they’ll be prompted during setup)
SDR qualifying questions (use on calls)
- “Who on your team has access to the Ribbn admin dashboard today?”
- “Do you already have the business + banking details handy for Stripe verification?”
- “Which country are you operating in?” (sets up expectations that payment methods vary by location)
Payment method availability varies by **business location** and **Stripe eligibility**. The safe claim is that Ribbn routes the merchant into Stripe to choose what applies.
Where Stripe is activated in Ribbn (quick product reference)
Activation happens inside Ribbn:
- Log in and open the Ribbn Admin Dashboard
- Navigate to Settings → Payments
- Click Activate Stripe
That’s the only “Ribbn side” setup SDRs should describe with confidence; after that, Stripe takes over for onboarding/config.
What gets configured during Stripe setup (and where)
After clicking Activate Stripe, Ribbn redirects to Stripe’s onboarding flow.
Setup checklist (SDR-safe)
| Setup item | Where it’s done | What to say (talk track) |
|---|---|---|
| Business & personal details | Stripe | “Stripe will verify the business—standard onboarding.” |
| Currency | Stripe | “You’ll pick the currency you accept payments in (e.g., SEK for Sweden).” |
| Payment methods | Stripe | “You choose the methods you want to offer—what’s available depends on your location and Stripe eligibility.” |
| Bank account for payouts | Stripe | “You connect the bank account where Stripe pays out.” |
Common “payment method” question (how to answer without overcommitting)
If asked: “Do you support Klarna / Swish / Amex?”
Use:
- “Ribbn connects you to Stripe, and Stripe determines which payment methods are available for your business based on location/eligibility. During Stripe onboarding you can select what applies.”
“Are we ready to take payments?” (definition of done)
A merchant is ready when:
- Stripe onboarding has been completed, and
- The Stripe integration becomes active (then they can accept payments).
Managing Stripe later (where to point customers)
If a prospect asks “What if we need to change something later?”:
- Go to Ribbn → Payments
- Click Go to Stripe Account
Use this to position Ribbn correctly: Ribbn is the operational home, Stripe is the payments configuration and refund home.
Refunds: set expectations clearly (and early)
Refunds **cannot be handled directly inside Ribbn** when using Stripe. **Customer refunds must be processed manually in Stripe.**
SDR phrasing that works
- “Ribbn tracks the order and operations, but the actual refund action happens in Stripe.”
- “If refunds are a daily workflow concern, we’ll make sure you see the Stripe handoff clearly in the demo.”
Quick “who does what” table (for objection handling)
| Task | Where it happens | Why it matters on a call |
|---|---|---|
| Connect/activate Stripe | Ribbn Admin | Simple activation path: Settings → Payments |
| Configure currency/payment methods/payout bank | Stripe (launched from Ribbn) | Stripe eligibility & localization live here |
| Issue customer refunds | Stripe Dashboard | Not available in Ribbn—don’t promise otherwise |
| Reopen/manage account connection | Ribbn → Payments | “Go to Stripe Account” is your bridge back |
How this fits Ribbn’s end-to-end resale story (keep it tight)
Stripe is one piece of the resale commerce engine Ribbn supports. Keep your narrative anchored in what the merchant actually needs:
- Inventory + webshop + POS: Ribbn runs the one-of-a-kind inventory lifecycle and supports in-store checkout and online selling.
- Multi-seller/consignment mechanics: Ribbn links items to sellers, tracks commissions, and supports payout readiness flows (manual and seller self payout in supported flows).
- Operational trust: clear lifecycle statuses (including sold/return-window gating) and transparent “where to do what” (refunds in Stripe).
If the conversation drifts into “Can you advise on our return policy, VAT, payout compliance, or financial setup?”: acknowledge and redirect—“We can show how the workflow behaves in Ribbn + Stripe, and loop in an AE/CS for policy-specific guidance.”
Objection handling (first-line, SDR-safe)
“We don’t want another system—can Ribbn just do refunds?”
- “Today, refunds for Stripe payments are processed in Stripe, not inside Ribbn. Ribbn gives you the connection point and operational context, and Stripe is the system that executes the refund.”
“Will all payment methods be available?”
- “It depends on your Stripe eligibility and location. During the Stripe onboarding Ribbn sends you into, you’ll see exactly which options you can enable.”
“Who owns payouts?”
- “Payout destination and payout configuration live in Stripe. Ribbn connects to Stripe and supports the resale operations around orders, sellers, and inventory.”
Discovery prompts to qualify payment fit (book better meetings)
Use these to determine whether payments are a core pain (or just a checkbox):
- Current stack
- “What are you using today for in-store payments and online payments?”
- Omnichannel reality
- “Do you sell in-store only, online only, or both?”
- Refund volume
- “How often are refunds happening today, and who processes them?”
- Ops ownership
- “Who would own payments setup (Stripe onboarding) on your team?”
Escalate / don’t commit (pricing & packaging guardrails)
Do not quote transaction fees, Stripe fee structures, or plan-specific pricing unless you have the current, approved pricing sheet in front of you. If asked, park it: “We’ll confirm pricing/fees in the meeting with an AE.”
Related internal references (for your own prep)
text
https://help.ribbn.ai/payments
https://help.ribbn.ai/how-do-i-integrate-stripe-as-payment-solution-to-my-ribbn-account