Payment providers
Connect Stripe, Polar or Dodo Payments so RamenID can create discount codes in your account.
RamenID creates every discount code directly in your own provider account. It needs to read your products and create discounts. It never reads your customers, payments or payouts.
Open Providers in the dashboard to connect. You can connect each provider once.
Connect with Stripe (when available) signs you in to Stripe and asks you to approve access. Stripe's own screen describes this as full access to the account, because Stripe Connect has no narrower option for creating coupons.
Or use a restricted key. In Stripe, go to Developers → API keys → Create restricted key and allow:
- Products: Read
- Coupons: Write
- Promotion codes: Write
Paste the key into RamenID. We check it by reading one product.
Test and live mode: whichever key you paste is the one we use. Use a test key (rk_test_...) to try things without real coupons.
What RamenID creates: a coupon limited to the rule's product with one redemption, and a promotion code (the code students type) with one redemption and a 7-day expiry.
Connect with Polar asks for these scopes: organizations:read, products:read and discounts:write.
Or use an Organization Access Token with products:read and discounts:write, from your organization's settings in Polar.
If your Polar account has several organizations, RamenID asks you to choose one after you connect. The connection shows Choose organization until you do.
RamenID uses Polar's production API. Polar's sandbox is not supported.
What RamenID creates: a percentage discount limited to the rule's product, with one redemption and a 7-day end date.
Paste an API key with write access from your Dodo Payments dashboard. Test and live keys are detected automatically.
What RamenID creates: a percentage discount restricted to the rule's product, usable once, expiring after 7 days. When a student gets a code, RamenID also creates a Dodo checkout session with the code already applied and their email filled in.
Connection status
| Status | What it means | What to do |
|---|---|---|
| Connected | Working | Nothing |
| Not connected | No connection yet | Connect |
| Choose organization | Polar connected, but no organization picked | Pick one |
| Key invalid | The provider rejected the key while creating a code | Paste a new key |
| Access revoked | The provider rejected the connection while creating a code | Connect again |
While a connection is broken, students who verify on its rules see "We could not create your discount code just now" and the verification shows Mint failed.
Disconnecting
Disconnecting removes its rules
Disconnecting a provider deletes every rule that uses it: their links stop working and they leave your rules table. Your verification history is kept, and codes already created in your provider stay there. Connecting again does not bring the rules back.
For Stripe and Polar connected through sign-in, disconnecting also revokes RamenID's access on the provider's side.
How credentials are stored
Keys and access tokens are encrypted at rest (AES-256-GCM) and never shown again after you save them.