Coinepay | How to Pay for Perplexity API with a Virtual Card (Step-by-Step)

The Perplexity API Platform is a pay-as-you-go service: instead of a monthly subscription, you buy prepaid credits that fund your API usage. This guide shows how to set up a Coinepay virtual card, add it to the Perplexity billing console, and buy credits, with a troubleshooting section for the most common reasons a card is declined. Prices and availability can change, so always confirm the current details on Perplexity's official documentation and in your Coinepay app.

Before you start: what you need

A verified Coinepay account. If you do not have one yet, register with Coinepay and complete identity verification (KYC) first. Card and fund services require this step.
A Coinepay virtual card with its card number, expiry date and CVV. These appear instantly in the dashboard or the iOS app or Android app.
Your real billing details — name, address and postcode — exactly as they are registered with Coinepay. Perplexity bills through Stripe, which checks this information.
A Perplexity account and access to console.perplexity.ai.

Use your genuine identity and billing data throughout. Entering invented addresses or trying to work around a region check can cause a decline and may breach Perplexity's terms.

Understand what you are paying for

The API Platform is separate from Perplexity's consumer and Enterprise subscriptions. Plan names like Standard (Free), Perplexity Pro, Perplexity Max, Education Pro, Enterprise Pro and Enterprise Max are not API pricing tiers — they do not fund API calls. API access is funded purely by prepaid credits.

Your usage tier (Tier 0 through Tier 5) is set by how much credit you have purchased over the lifetime of the project — at the time of writing (October 2026) the documented thresholds are $0, $50, $250, $500, $1,000 and $5,000. These tiers govern rate limits and access, not a monthly price.

The documented APIs include the Orchestrator API, Agent API, Search API, Embeddings API and Decisions API. Prices seen on October 2026 include the Search API at $5 per 1,000 successful requests (or $1 per 1,000 with Fast Search, introduced September 2026), where one request can contain up to five queries. Embeddings and Decisions API models are priced per million tokens. Because these rates vary by model and can change, treat them as examples only and check the official Perplexity pricing page before you buy.

Step 1: Create or top up your Coinepay virtual card

Sign in to Coinepay and open the card section of the dashboard or app.
Create a virtual card (or choose an existing one). The card number, expiry and CVV are shown instantly.
Make sure the card balance comfortably covers your intended credit purchase. The Perplexity billing form currently enforces a minimum, so a very small balance will not be enough — see the troubleshooting section below.

If you run API usage for ad accounts or other business workloads, you can create a dedicated card per project and set a custom spending limit on each one to keep budgets separate.

Step 2: Set up your Perplexity API project

Create a Perplexity account and sign in at console.perplexity.ai.
Set up a Project. Billing changes require Admin permissions, so use an account with the right role.
Generate an API key inside the project when you are ready to start building. Adding credits is what enables real usage.

Step 3: Add your Coinepay card in Billing

In the console, open Project → Billing. Here you can see your balance, payment method, usage and invoices.
Select Add payment method (or Manage) to open the Stripe portal.
Enter your Coinepay virtual card number, expiry date and CVV, then the billing address and postcode that match your Coinepay registration.
Save the card. Adding a payment method does not itself charge it.

The current API billing instructions specify a credit card processed through Stripe. Whether specific card networks, debit cards or prepaid cards are accepted at direct API checkout is not publicly confirmed, and the card acceptance listed for Enterprise subscriptions should not be assumed to apply here. If you want certainty before buying, contact Coinepay support to confirm your card meets this requirement, and review Perplexity's documentation for its accepted methods.

Step 4: Buy credits (or set auto reload)

In Project → Billing, choose Buy more credits for a one-time manual purchase.
To automate top-ups, open Change preferences → Auto reload and set your trigger and reload amount.
Confirm the charge. When credits run out, API keys are blocked until you replenish the balance, so keeping a buffer avoids interruptions.

There is also an API Platform Credits offer on AWS Marketplace that starts at $1,000 on a one-month contract; AWS handles that purchase's invoicing, and you complete post-purchase registration so the credits and project are provisioned. That route uses your AWS billing rather than a card entered in the Perplexity console.

Troubleshooting a declined card

Stripe, the documented processor, returns a range of decline codes. The exact cause for any one customer is not something the console always spells out, so work through these common possibilities:

Amount below the minimum. A reported billing-form message, "Amount too low. Please enter an amount of at least $50.", appears when the recharge amount is too small; a $50 minimum auto-recharge amount was confirmed as an intended change in April 2026. Enter at least the required minimum.
Insufficient balance. Make sure your Coinepay card holds enough to cover the full credit purchase. Top it up in the app and try again.
Billing address or postcode mismatch. The address and postcode in Stripe must match what is on file for your Coinepay card. Re-enter them carefully.
Incorrect CVC or expired details. Re-check the CVV and expiry shown in your Coinepay dashboard, and confirm the card is active.
3-D Secure / required authentication. If an extra verification step is requested, approve it through Coinepay. Watch for any prompt in the app.
Unsupported card or currency / region checks. API fees are specified in USD, and the terms prohibit use involving US-embargoed countries and prohibited-party lists. Availability should not be inferred solely from whether a card can be entered. If your card or region is refused, do not try to disguise your location — confirm your card details with Coinepay support and check Perplexity's documentation.

Not every error is a card problem. Perplexity notes that an HTTP 401 can mean an invalid or deleted key or exhausted credits, and 429 means a rate limit. Check your project's credit balance before treating either as a failed card payment.

Stopping charges and refunds

Because ordinary API access is pay-as-you-go, there is no subscription to cancel. To stop future charges, check or disable Auto reload in your billing preferences and stop making API calls. The API terms state payments are non-refundable unless expressly stated otherwise; an older company FAQ mentions a refund within 14 days of purchase when no credits have been used, but whether that still governs every direct purchase is not confirmed. For direct API questions, Perplexity lists [email protected]; AWS Marketplace refunds are requested from [email protected] with the order ID.

Managing it all from Coinepay

You can monitor the card you use for Perplexity from the 24/7 Coinepay dashboard and app — view transactions, adjust limits and top up at any time. For help with card creation, verification or a payment that did not go through, reach out via Coinepay support or our Telegram channel. You can also start from the Coinepay home page.

Get your Coinepay virtual card: Sign up · App Store · Google Play · Customer support

FAQ

Does the Perplexity API require a subscription?

No. The API Platform is pay-as-you-go and funded by prepaid credits. Consumer and Enterprise plan names such as Perplexity Pro or Max are not API pricing tiers and do not fund API calls.

Where do I add my card for the Perplexity API?

Sign in at console.perplexity.ai, open Project → Billing, and choose Add payment method or Manage to reach the Stripe portal. Enter your Coinepay virtual card number, expiry, CVV and matching billing address. Adding a card does not charge it.

Why was my card declined when buying credits?

Common causes include an amount below the $50 minimum, insufficient card balance, a billing address or postcode mismatch, an incorrect CVV, an expired card, a required 3-D Secure step, or an unsupported card/currency. Check each and confirm your card details in the Coinepay app.

Is a Coinepay virtual card accepted at Perplexity API checkout?

The API billing instructions specify a credit card via Stripe, but acceptance of specific card networks, debit or prepaid cards at direct API checkout is not publicly confirmed. Contact Coinepay support to confirm your card meets the requirement, and check Perplexity's documentation before buying.

Can I stop future charges or get a refund?

There is no subscription to cancel; disable Auto reload in billing preferences and stop API usage. API payments are non-refundable unless stated otherwise, though an older FAQ mentions refunds within 14 days if no credits were used. Contact [email protected], or [email protected] for AWS Marketplace orders.

How to Pay for Perplexity API with a Virtual Card (Step-by-Step)