Nocturne Shadow vs Aurora Limits: Expected Monthly Spend Caps, Auth Holds, and Refund/Partial Capture Effects ($25 vs $50)

Nocturne virtual card transaction limits Shadow vs Aurora come down to the tier you buy: Nocturne Shadow costs $25 and Nocturne Aurora costs $50, with Aurora built for higher expected spend before limit-based declines. If a charge is blocked by the card limit, the usual result is an authorization declined event, not a completed payment needing a refund.

Price first: what you pay and how limits show up in real spend

Nocturne sells no-KYC virtual debit card access for privacy-focused buyers who want to spend crypto through a virtual Visa/Mastercard-style card flow. You fund on-chain, mint the card, and use a tokenized card number at checkout; the merchant sees card number details, not your crypto wallet or identity documents.

The two relevant tiers are simple:

• Nocturne Shadow: $25 upfront
• Nocturne Aurora: $50 upfront
• Per-payment fee: $0.30 per payment
• Monthly fee: $0
• Onboarding: no ID / no KYC
• Funding: fund on-chain, including privacy-focused crypto users such as XMR/Monero holders where supported by the funding path

The cost question and the limit question are connected. Shadow has the lower entry cost and is the better fit for smaller, less frequent purchases. Aurora costs $25 more upfront and is the better fit when your expected monthly spend, daily bursts, or larger single payments would otherwise run into Nocturne spending limits.

The key operational rule: limits are checked at transaction authorization. If the authorization amount is above the available card balance or above the applicable per-transaction limit, daily spend limit, or monthly spend limit, the merchant may receive a merchant decline due to limit. That failed attempt is not the same as a captured charge.

One table: Nocturne Shadow vs Aurora pricing + expected limit behavior at a glance

Item	Price range	Expected limit behavior
Nocturne Shadow	$25 upfront	Lower practical ceiling; best for smaller payments, lighter daily spend, and buyers who can split purchases below the per-transaction limit
Nocturne Aurora	$50 upfront	Higher practical ceiling; better for larger carts, higher daily cadence, and users closer to a monthly spend limit
Per approved payment	$0.30 flat fee per payment	Applies to successful payment activity; do not plan around a fee saving from repeated declined attempts
Monthly card fee	$0/month	No monthly fee, so cost is mainly upfront tier price plus payment count
Typical blocked purchase outcome	$0 captured when blocked before approval	Authorization declined or void authorization behavior, not a normal refund after capture

Nocturne does not require a bank account or exchange login to start the card flow. The buyer funds the card path on-chain, mints the virtual card in about 60 seconds when the flow is available, and then uses the virtual card authorization limits attached to that card tier.

What drives Nocturne transaction limits: tier, cadence, and windows

What transaction limits should I expect on Nocturne Shadow ($25) vs Aurora ($50)?

Expect Nocturne Shadow to be the lower-cost, lower-capacity option and Nocturne Aurora to provide more room for larger or more frequent purchases. Shadow is the $25 card for lighter spending. Aurora is the $50 card for users who expect a higher monthly spend limit, more daily activity, or fewer declines on larger carts.

The exact decline point depends on the live card settings shown when you mint and use the card. Treat the displayed card limits as the source of truth. The practical comparison is still straightforward: Shadow is cheaper but reaches limits sooner; Aurora costs $25 more but is designed for higher spend capacity.

Are the limits per payment, per day, or per month on a rolling window?

Nocturne limits can matter at three levels:

1. per-transaction limit: the maximum amount one authorization can request.
2. daily spend limit: the maximum approved spend across a day-like period.
3. monthly spend limit: the maximum approved spend across a month-like period.

Where a rolling-window month applies, do not assume the cap resets at midnight on the first day of the calendar month. A rolling-window month can count activity over the trailing period instead. That means a payment made 20 days ago may still reduce today’s remaining limit until it ages out of the rolling window.

This is the card limit impact on retries: retrying immediately with the same amount usually fails if the original reason was a limit. A retry works only when the new authorization fits inside the available per-payment, daily, and monthly room.

How limit checks interact with refunds: declined versus captured

What happens when a merchant tries to authorize a charge above my Nocturne limit?

The merchant sends a transaction authorization request for the full amount. If that amount is above the active limit or available balance, the authorization declined result stops the payment before capture. The merchant may show “payment failed,” “card declined,” or “unable to authorize.”

For example, assume a Shadow card has $180 of remaining room under the relevant limit and a merchant attempts a $220 authorization. The $220 request is blocked. The merchant has no approved authorization to capture, so the order should not be treated as paid.

If an authorization is declined, do refunds still happen—or is it a voided authorization instead?

If the authorization is declined, there is typically no settled card charge to refund. You may see a pending attempt disappear, a void authorization, or no completed transaction at all. That is different from auth holds and refunds after an approved transaction.

A refund after capture only makes sense when the payment first passed authorization and was later captured by the merchant. If the first step failed, the practical action is to retry a payment with a smaller amount, wait for limit capacity to return, or use a card tier with more room.

How limit checks interact with partial captures

How do refunds work when a purchase is authorized first and then captured?

Capture vs authorization matters. Authorization reserves approval for an amount. Capture is the merchant’s later step to finalize all or part of that amount. Once capture happens, a later return, cancellation, or adjustment can create a refund after capture.

Example: a merchant authorizes $120, captures $120 the next day, and then cancels the order. The refund is a normal refund after capture. Refund timing depends on the merchant, processor, network handling, and card posting cycle. It is not instant simply because the card was no-KYC.

What changes for partial captures, split shipments, or incremental charges?

A partial capture happens when the merchant authorizes one amount but captures less. This is common with a split shipment. For example, a store authorizes $150 for three items, ships one item now, and captures $60. The remaining $90 may be released, adjusted, or captured later depending on the merchant’s flow.

Partial capture refunds can be confusing because the unused authorization amount is not always a “refund.” If $150 was authorized and only $60 was captured, the remaining $90 may simply be released from the hold. If $150 was captured and $90 is returned later, that is a refund.

Incremental charges add another limit issue. If a merchant tries to increase an approved amount from $80 to $115, the new authorization or adjustment may be checked against remaining card limits. If the increase exceeds the per-transaction or daily room, the extra charge can be declined even though the first $80 authorization succeeded.

Example scenarios with numbers: blocked auths, retries, captures, and refunds

Scenario 1: blocked authorization above the per-payment limit

A buyer tries a $310 cart on a card with a $250 per-payment ceiling. The transaction authorization is rejected. Result: authorization declined, $0 captured, no refund needed. The buyer should retry a payment at $250 or less, or split the order if the merchant supports separate charges.

Cost if the $250 retry succeeds: $250 purchase amount plus the $0.30 per payment fee. Cost if the $310 attempt never authorized: do not treat it as a completed $310 purchase.

Scenario 2: daily limit reached after several small orders

A buyer makes four successful $45 payments in one day, totaling $180. Each approved payment carries a $0.30 fee, so the payment fees total $1.20. If the applicable daily spend limit leaves only $20 of room, a fifth $35 purchase can be declined even though it is small.

The fix is not to keep clicking pay. Wait until daily capacity returns or reduce the next authorization to $20 or less, assuming the merchant accepts that amount.

Scenario 3: rolling monthly spend window blocks a retry

A buyer has $40 of remaining monthly capacity under a rolling monthly spend window and attempts a $75 subscription renewal. The merchant receives a decline. Retrying the same $75 immediately should fail again because the rolling window has not changed.

A workable retry amount would need to be $40 or less, or the buyer must wait until older approved spend leaves the rolling-window month. This is why subscriptions should be sized below the available monthly room before the renewal date.

Scenario 4: authorized first, then partial capture

A merchant authorizes $200 for a multi-item order. Only one item ships, so the merchant uses a partial capture of $80. If the other $120 is never captured, the remaining hold should be released or voided according to the merchant and processor timeline.

Fee planning: the completed captured payment is the meaningful payment event. Avoid assuming that every visible authorization line is a final charge.

Scenario 5: captured charge, then refund timing

A buyer pays $95 and the merchant captures the full amount. The buyer cancels after shipment processing, and the merchant issues a $95 refund. That is a refund after capture, so refund timing can take several business days depending on the merchant’s processing and the card network path.

If the buyer tries another $95 purchase before the refund posts, the old spend may still count against available card room. That can trigger a limit-related decline even though a refund is pending.

FAQ: Limits, declines, refunds, and partial captures for Nocturne Shadow/Aurora

Does the $0.30 per payment fee apply when a transaction is declined versus captured?

The $0.30 flat fee per payment is tied to payment activity, not a strategy of repeated failed attempts. If a transaction is declined before approval, do not treat it like a captured purchase. Still, the safest cost practice is to avoid repeated declines and size the authorization correctly before retrying.

If my first attempt is blocked by limits, when should I retry and how do I size the retry amount?

Retry only after you know which limit was hit. If the issue was the per-transaction limit, lower the purchase amount below that cap. If the issue was the daily spend limit, wait for daily room to return. If it was the monthly spend limit on a rolling-window month, wait until older spend rolls off or use a smaller amount within the remaining room.

How can I reduce the chance of limit-related declines for subscriptions or multi-item orders?

Keep subscription renewals below the known remaining monthly and daily room. For multi-item orders, avoid carts that may trigger large preauthorizations, split shipment behavior, or later incremental captures above the original amount. Aurora is usually the better fit when larger recurring payments would push Shadow too close to its limits.

Which tier should I choose if I want fewer merchant declines?

Choose Nocturne Shadow if your payments are small and occasional. Choose Nocturne Aurora if your carts, subscriptions, or daily purchase cadence are more likely to hit a card limit. Aurora costs $50 instead of $25, but the extra upfront cost can reduce failed checkout attempts for higher-spend users.

What does the merchant see when I pay?

The merchant sees a card transaction and card details needed for checkout. With a Nocturne no-KYC virtual debit card, the merchant does not see your on-chain wallet as the payment instrument; the checkout uses the tokenized card number and normal card authorization flow.