All articles

Nocturne14 min read

Nocturne’s $0.30 Flat Fee Explained: Which Payment Steps It Covers (Auth, Capture, Retries, Tips)

See exactly when Nocturne’s $0.30 flat fee applies across authorization, capture, declines, retries, tips, funding, and card minting.

No KYC Cards Guide

The Nocturne $0.30 flat per-payment fee applies when a Nocturne virtual debit card transaction runs through a payment attempt that reaches the authorization/capture path. It is not a card minting fee, account funding fee, or monthly fee. If checkout creates multiple charge attempts, the $0.30 can repeat per attempt.

Quick cost answer: what you should expect to pay

For a normal single checkout, Nocturne’s payment fee is simple: $0.30 flat fee per payment. If one merchant charge goes through once, your Nocturne fee for that payment is $0.30.

Where users get surprised is not the fee amount. It is the number of payment events created by the merchant, processor, terminal, or checkout flow.

A clean online merchant checkout might create one authorization (auth) and one capture for the same purchase. That typically counts as one payment event from the user’s perspective, so the Nocturne fee is $0.30. A messy checkout can create a decline, a retry, a corrected attempt, a tip adjustment, or a second authorization. Those steps can make the total fee $0.60, $0.90, or more, even when the product price did not change much.

Nocturne publishes this cost-breakdown guide so you can understand exactly what the $0.30 flat per-payment fee covers when using a no-KYC virtual card checkout and what it does not cover. This guide focuses on practical checkout behavior: authorization, capture, retries, declines, tips, and what you may see at an online merchant or in-person terminal.

Item or checkout event Nocturne fee range
Card minting $0 Nocturne per-payment fee; card product cost is separate
Nocturne Shadow card $25 card price
Nocturne Aurora card $50 card price
Account funding / on-chain top-up $0 Nocturne per-payment fee
Monthly plan $0 monthly fee
One successful merchant payment $0.30
Auth and capture for the same final payment Usually $0.30 total
Decline followed by one retry Usually $0.30–$0.60 depending on whether each attempt reached billable payment processing
Two merchant retries after a failed attempt Up to $0.90 total across three attempts
Tip included in same authorization/capture flow Usually $0.30 total
Tip processed as a separate authorization or adjusted final payment event Usually $0.30–$0.60 total

Nocturne is built for privacy-seeking consumers who want crypto-funded Visa/Mastercard network card spending without ID onboarding. You mint a Nocturne virtual debit card, fund on-chain, and spend with a tokenized card number so the merchant sees card credentials, not a bank account or exchange login. The checkout fee is intentionally narrow: a per-payment flat fee, not an ongoing account plan.

What the $0.30 flat per-payment fee applies to in plain checkout terms

The $0.30 flat fee applies per payment when you use a Nocturne virtual debit card for a merchant transaction. Think of it as attached to a card payment attempt that enters the card-processing path, not to your account existing.

In plain language, it applies to merchant payment activity such as:

  • Paying an online merchant with your Nocturne card number.
  • Using the card at an in-person terminal where virtual card acceptance is supported.
  • A checkout attempt that sends an authorization request and moves into a payment flow.
  • A merchant retry that creates another payment attempt.
  • A final charge that includes a tip, if the merchant processes it as part of the payment.

It does not apply to:

  • Opening a Nocturne account.
  • No-KYC onboarding.
  • Card minting itself.
  • Buying the Nocturne Shadow ($25) or Nocturne Aurora ($50), except for the separate card price.
  • Funding the card on-chain.
  • Holding the card month to month.
  • Logging into an exchange, because Nocturne does not require an exchange login to spend.

That distinction matters. Nocturne virtual debit card fees are designed around actual payment use. You pay when you make payment attempts, not because you keep the card active.

The simplest rule

If the merchant creates one payment, expect one $0.30 fee.

If the merchant creates two payment attempts, expect the possibility of two $0.30 fees, or $0.60 total.

If the merchant creates three payment attempts, the Nocturne fee can reach $0.90 total.

The number that matters is not how long you spend on the checkout page. It is how many card payment attempts the checkout produces.

Auth vs capture: where the $0.30 typically shows up

Does Nocturne’s $0.30 apply to authorization or capture?

The practical answer: the $0.30 is tied to the payment flow that begins with authorization (auth) and ends, if successful, in capture. In normal card processing, auth checks whether the card can support the transaction. Capture is the merchant’s step to finalize the charge and collect funds.

For a standard purchase, you usually do not pay $0.30 for auth and another $0.30 for capture when they are two steps of the same final payment. The expected fee is $0.30 total for that payment.

Example:

  • Product price: $42.00
  • Merchant sends auth: $42.00
  • Merchant captures: $42.00
  • Nocturne fee: $0.30
  • Total impact before any merchant taxes or shipping: $42.30

This is the cleanest authorization capture fee timing case: one authorized purchase, one captured payment, one per-payment fee.

Why auth and capture can feel confusing

Many merchants do not capture immediately. Hotels, delivery apps, restaurants, gas stations, and some e-commerce platforms may authorize first and capture later. You may see a pending amount before the final amount settles.

That does not automatically mean multiple Nocturne fees. If the merchant is simply moving one purchase from auth to capture, it is generally one payment.

The fee count can change when the merchant creates a new attempt instead of completing the original one. That can happen when:

  • The first authorization fails.
  • The merchant changes the amount and sends a fresh authorization.
  • The checkout retries after a network or processor error.
  • The user edits billing details and submits again.
  • A tip is processed separately instead of as an adjustment to the same payment.

In short: auth plus capture for one purchase usually means $0.30. Auth, failure, retry, and then a new auth can mean $0.60 or more.

Declines & retries: when the $0.30 can repeat

When a payment is declined, do you still pay the $0.30 fee?

A declined transaction fee depends on whether the declined attempt reached the billable card-payment path. If the checkout fails before a real card attempt is created, such as a form validation error before submission, you should not treat that as a payment fee event. But if the merchant sends a real authorization request that is declined, that attempt can still count as a payment attempt.

Practical range:

  • Typo caught before submission: usually $0.00 Nocturne payment fee.
  • Merchant-side validation before card network attempt: usually $0.00.
  • Actual card authorization request that declines: can be $0.30.
  • Decline plus successful retry: can be $0.60 total.

Example:

  • Attempt 1: $75.00 purchase, AVS/CVV mismatch, authorization request sent and declined.
  • Nocturne fee on attempt 1: $0.30 if it reached billable processing.
  • Attempt 2: user corrects details, $75.00 approved.
  • Nocturne fee on attempt 2: $0.30.
  • Total Nocturne fees: $0.60.

This is why users should distinguish a rejected web form from a real card decline. A checkout page saying “fix your ZIP code” before submitting is different from a card network decline after the merchant tried to authorize the transaction.

If the merchant retries the charge, does the $0.30 fee repeat?

Yes, if the merchant retry creates another payment attempt, the payment retries fee can repeat. Nocturne’s fee is per payment attempt that enters the processing flow, not per shopping cart.

Example:

  • Cart total: $18.00
  • First attempt: processor timeout after authorization request
  • Fee: $0.30
  • Second attempt: merchant automatically retries
  • Fee: $0.30
  • Final successful charge: $18.00
  • Total Nocturne fees: $0.60

If the merchant retries twice, the fee can be:

  • Attempt 1: $0.30
  • Attempt 2: $0.30
  • Attempt 3: $0.30
  • Total: $0.90

This is the main situation that makes a small flat fee look larger than expected.

Is the $0.30 fee charged per merchant attempt or per final successful charge?

Use this rule: the fee is best understood as per merchant payment attempt that reaches the authorization/capture flow, not only per final successful charge.

For a single clean purchase, that distinction does not matter. One final successful charge equals one payment event, so the fee is $0.30.

For a failed checkout, it matters. A merchant may create multiple attempts before one succeeds. Each attempt can carry its own $0.30 if it reaches the billable payment path.

Tips: whether a tip is one payment or multiple payments

How do tips work—are they added as part of the same payment or a separate authorization?

Tipping with virtual cards depends on how the merchant or terminal handles the final amount. Tips are usually one of three patterns:

  1. Tip selected before authorization.The merchant authorizes the meal, ride, delivery, or service with the tip included. This is usually one payment and one $0.30 fee.

  2. Tip adjusted after authorization but before final capture.The merchant initially authorizes a base amount, then captures the final amount including the tip. If this remains one payment flow, it is usually one $0.30 fee.

  3. Tip processed as a separate charge or fresh authorization.The base payment and tip become separate payment attempts. This can create two $0.30 fees.

Example, tip included upfront:

  • Food order: $30.00
  • Tip: $6.00
  • Authorized amount: $36.00
  • Nocturne fee: $0.30
  • Total charged by merchant plus Nocturne fee: $36.30

Example, separate tip event:

  • Base service charge: $30.00
  • Nocturne fee: $0.30
  • Separate tip charge: $6.00
  • Nocturne fee: $0.30
  • Total Nocturne fees: $0.60
  • Total charged by merchant plus Nocturne fees: $36.60

The safest assumption: if the tip changes the same authorized/captured payment, expect one fee. If the tip becomes a separate authorization, expect another $0.30.

What can change the total cost and what won’t

The amount of the fee does not change with cart size. A $9.00 purchase and a $900.00 purchase both have the same Nocturne per-payment fee if each is one payment: $0.30.

What changes the total is the count of payment attempts.

What situations make the $0.30 total higher than expected at checkout?

The total can rise when checkout creates more than one payment event. Common causes include:

  • A decline followed by a retry.
  • Incorrect billing details causing AVS/CVV mismatch after authorization is attempted.
  • 3DS challenges that fail and cause the merchant to reattempt payment.
  • Merchant processor timeouts.
  • User clicking “Pay” more than once.
  • Merchant splitting an order into multiple shipments or partial captures.
  • Tip handled as a separate authorization.
  • Subscription merchant running a test authorization and then a real charge.
  • In-person terminal reversal followed by another attempt.

These situations do not change the $0.30 flat fee itself. They change how many times it is applied.

Does $0.30 apply to auth failures during checkout (3DS challenges, AVS/CVV mismatch)?

It can. If the failure occurs before a card authorization is sent, there is usually no per-payment fee. If the checkout sends an auth request and it fails because of 3DS, AVS, CVV, balance, merchant category, processor routing, or similar checks, the attempt can count.

Concrete examples:

  • User enters invalid email format; checkout blocks submission: $0.00 fee.
  • User enters wrong CVV; merchant sends authorization; decline occurs: possible $0.30 fee.
  • 3DS challenge fails before payment attempt is completed: often $0.00, but depends on whether an auth was sent.
  • 3DS passes, auth declines for another reason: possible $0.30 fee.

The user-visible error message may not tell you exactly which stage failed. The practical prevention step is to reduce avoidable retries.

Are $0.30 fees charged for card minting, account funding, or monthly plans?

No. The $0.30 flat fee is for payment activity, not card creation or account maintenance.

  • Card minting: no $0.30 payment fee.
  • Nocturne Shadow: $25 card price.
  • Nocturne Aurora: $50 card price.
  • On-chain funding: no $0.30 payment fee from Nocturne.
  • Monthly plan: no monthly fee.

Nocturne’s model is designed for users who want a no-KYC card, no bank account, no exchange login, and a clear per-payment cost.

How can I reduce retry-driven extra $0.30 charges?

You cannot control every merchant processor decision, but you can reduce avoidable repeats:

  • Check the card balance before paying.
  • Confirm billing ZIP, CVV, and expiry before submission.
  • Avoid clicking the pay button multiple times.
  • Wait after a timeout before submitting again.
  • Use merchants with clear card checkout flows.
  • For tips, choose the final tip before authorization when possible.
  • Avoid merchants that split one order into many separate charges if fee predictability matters.
  • Keep enough funded balance to cover the purchase, tip, taxes, shipping, and the Nocturne fee.

The goal is simple: one clean merchant attempt equals one $0.30 fee.

Do online merchants and in-person terminals behave differently for fee counting?

They can. An online merchant often shows a checkout page, sends an authorization, and captures immediately or later. An in-person terminal may authorize, reverse, adjust, or retry based on terminal rules, connectivity, tip settings, or card-present/card-not-present handling.

Fee counting still follows the same principle: one payment attempt that enters the payment flow can mean one $0.30 fee. More attempts can mean more fees.

Examples:

  • Online merchant, one checkout submit, approved: $0.30.
  • Online merchant, failed AVS then corrected retry: $0.60 possible.
  • In-person terminal, base amount plus tip in one final capture: $0.30 usually.
  • In-person terminal, first tap fails then terminal retries as a new attempt: $0.60 possible.

Nocturne gives you a tokenized card number for card spending, but the merchant’s checkout system still controls how many attempts it sends.

Example scenarios with exact numbers

Scenario 1: Clean online purchase

You buy software from an online merchant.

  • Product: $49.00
  • Tax: $0.00
  • Merchant payment attempts: 1
  • Authorization: approved for $49.00
  • Capture: $49.00
  • Nocturne fee: $0.30
  • Total: $49.30

Fee count: one payment, one fee.

Scenario 2: Decline, then corrected retry

You enter the wrong CVV on the first attempt, then correct it.

  • Cart: $64.00
  • Attempt 1: auth sent, CVV mismatch, declined
  • Fee on attempt 1: $0.30 possible
  • Attempt 2: corrected details, approved
  • Fee on attempt 2: $0.30
  • Merchant charge: $64.00
  • Total Nocturne fees: $0.60
  • Total: $64.60

Fee count: two payment attempts, two possible fees.

Scenario 3: Merchant timeout and automatic retry

The merchant’s processor times out and retries automatically.

  • Cart: $120.00
  • Attempt 1: authorization request sent, timeout
  • Fee: $0.30
  • Attempt 2: retry approved and captured
  • Fee: $0.30
  • Merchant charge: $120.00
  • Total Nocturne fees: $0.60
  • Total: $120.60

Fee count: not based on your clicks; based on merchant attempts.

Scenario 4: Tip included in the original payment

You place a delivery order and add tip before checkout.

  • Food subtotal: $28.00
  • Delivery fee: $4.00
  • Tip: $5.00
  • Final merchant amount: $37.00
  • Payment attempts: 1
  • Nocturne fee: $0.30
  • Total: $37.30

Fee count: tip is part of the same payment.

Scenario 5: Tip processed separately

A service provider charges the base amount first, then processes a separate tip.

  • Base charge: $40.00
  • Fee for base payment: $0.30
  • Separate tip charge: $8.00
  • Fee for tip payment: $0.30
  • Merchant total: $48.00
  • Nocturne fees: $0.60
  • Total: $48.60

Fee count: two payment events.

Scenario 6: Three attempts before success

A merchant checkout fails once for address verification, then again after a processor retry, then succeeds.

  • Cart: $90.00
  • Attempt 1: AVS mismatch decline: $0.30 possible
  • Attempt 2: retry timeout: $0.30 possible
  • Attempt 3: approved: $0.30
  • Merchant charge: $90.00
  • Total Nocturne fees: up to $0.90
  • Total: up to $90.90

Fee count: the $0.30 did not increase; the number of attempts did.

Quick FAQ so you can predict your checkout total

1. Does Nocturne charge $0.30 for every authorization and every capture separately?

Usually no. A normal authorization and capture for the same final payment is typically one payment event, so the expected Nocturne fee is $0.30 total. A new authorization or retry can create another $0.30 fee.

2. If a card payment is declined, is the $0.30 always charged?

Not always. If the checkout fails before a real card attempt, there is usually no fee. If an authorization was sent and declined, the declined attempt can carry the $0.30 fee.

3. Do retries count as new payments?

They can. If the merchant retry creates a new payment attempt, the $0.30 per-payment flat fee can repeat. One retry after one failed attempt can make the Nocturne fee $0.60 total.

4. Are card purchase, funding, or monthly maintenance included in the $0.30 fee?

No. The $0.30 is not for card minting, on-chain funding, or a monthly plan. Nocturne Shadow costs $25, Nocturne Aurora costs $50, and Nocturne has no monthly fee.

5. What is the best way to estimate the fee before paying?

Count expected payment attempts. One clean checkout is $0.30. A decline plus retry can be $0.60. Three attempts can be $0.90. If a tip is processed separately, add another $0.30.

Topics

  • Nocturne
  • virtual debit card
  • fees
  • no-KYC
  • checkout