Fees

• $5.00 is charged per card, and it includes the card’s first month of management (until the first monthly charge falls due).
• The fee is reserved from your available wallet balance before the issuing request is sent, and finalized when the provider creates the card.
• A definite rejection releases the reservation. If the outcome is uncertain, the fee remains held until the request is reconciled.
• Your balance has to cover the fee at that moment. If it does not, the request cannot be completed.
• The fee is one-off per card and is not returned when a card is closed or the paid service is ended: it pays for the creation of that card.
• The card product is a single USD product, Services & Advertising, issued by the external provider under its permitted merchant categories.

• From the month after issuance, each card costs $3.00 per calendar month. Each month is billed once.
• A month falls due one calendar month after the card was created, and again on each monthly anniversary after that, counted in UTC. Where the anniversary day does not exist in a short month, the charge falls on that month’s last day; the original day stays the anchor for later months.
• The charge is taken from your wallet balance. The balance is never allowed to go negative, and a card’s own balance is never used to pay it.
• If the balance is too low, the month stays unpaid and overdue. Nothing is frozen automatically — the provider’s API cannot undo a freeze — and the unpaid amount is caught up when the balance allows it. While a management charge is unpaid, new card and card-funding requests are refused until it is settled; a withdrawal request would also be refused where a payout route is available.
• A frozen card keeps accruing the management charge while it remains open in your account. This is Pepe Pay’ own fee under this tariff, not a charge passed through from the provider: the two are separate, and the provider states that blocked cards are not subject to its own maintenance charges. Freezing does not pause this management fee; only a closed card or a completed paid-service exit does.
• Where the issuing provider supports closing a card, closing it stops future charges and cancels unpaid periods: a closed card is not charged afterwards. The provider available in the current build has a block operation but no close or unblock operation, so the app cannot close or unfreeze a card.
• You can request the end of Pepe Pay’ paid management service for a card in the app. This is separate from the issuer card’s status: Pepe Pay never blocks or closes the issuer card automatically, and ending the paid service does not by itself block or close it. The provider available in the current build has no close operation, so the exit can complete only if the request opted in to blocking the card. While a request is pending, monthly fees continue on the usual UTC anniversary. The exit completes only after a fresh issuer read confirms the card is blocked or closed and no unresolved card funding, fee or payment remains. Completion cancels unpaid periods under the closed-card convention, keeps already-paid periods and their receipts, and does not enrol the card again. Paid periods are not refunded. Any balance still on the issuer card is recorded for operator follow-up; ending the paid service does not automatically return it or credit your wallet, and there is no general self-service crypto payout of that residual. Contact support through the contact page about residual-balance settlement. Only the card’s owner can fund it, change its controls, manage its billing or request this exit; a team member cannot.
• Where an exit request asks Pepe Pay to block the card, that uses the provider’s block operation and cannot be undone in the app if the provider has no unblock operation. A completed exit cannot be cancelled. A pending request remains visible with the reason it has not completed.
• Pepe Pay may send at most one Telegram reminder per billing period, no earlier than 72 hours before the due time, or after a period is actually overdue. A reminder states the amount, the UTC due date and the masked card suffix; it never contains card credentials or codes. Delivery is best-effort: a failed or unconfirmed send is recorded but not retried, because Telegram has no idempotency key, so a reminder is never a guarantee that a charge was announced. The billing notice in the app is the durable record.
• Each card stays on the versioned tariff it was issued under. This tariff applies to cards issued under it, is not applied retroactively, and cards created before it was published are not enrolled.
• Nothing is charged before you accept the tariff for a new card: the Mini App shows the fees and the tariff version, and asks for your confirmation before the request is sent.

New deposits use the configured Pepe Pay USDT-TRC20 receiving wallet. These are Pepe Pay payment requests, not Spendge invoices. Use only the active invoice shown in your account; the page below is not itself a payment instruction.

Scroll horizontally to see all columns.

• Automatic wallet credit, separate card funding. Pepe Pay detects the exact transfer and checks its canonical blockchain receipt. Once the payment is final, it credits the accepted net amount to your internal USD wallet. This new route is backed by received USDT in our own wallet; it does not query or verify Spendge USD reserve and does not transfer funds to Spendge automatically. The operator funds the issuer separately and executes card-funding requests.
• The provider’s current preview applies a 1% card-product fee when its fiat USD is moved to the card account. It is a provider charge, separate from the Pepe Pay deposit fee, and this page does not present it as zero. Nothing in the worked examples below includes it.
• Existing balances and request references are preserved. Unresolved invoice or settlement operations require support; a provider account balance alone does not prove an individual invoice was received or settled.
• Historical invoice amounts, expiry and accepted fee snapshots remain records of the original request, not authorization to send a new payment. Do not pay an expired invoice or reuse an earlier request’s instructions.
• Previously accepted own-wallet requests keep their original route, receiving address, identification fraction and fee snapshot. They are not converted into customer-paid invoices or silently marked settled. After any request is paid, never send again, even if a message asks for it.
• Pepe Pay charges $1.50 plus 5% of the requested base amount on each deposit, deducted from the amount: a $100.00 base deposit credits $93.50 to your balance. The percentage part is rounded up to the next whole cent, so at the $50.00 base minimum the fee is $4.00 and the credit is $46.00.
• Only the percentage part is calculated on the base amount; the fixed part is charged once per deposit. Own-wallet invoices include a small identification fraction in the exact six-decimal amount. That fraction is not credited and carries no fee. Historical customer-paid Spendge invoices had no such fraction. Blockchain network fees are separate.
• The base amount is credited at one dollar per token, with no market conversion applied, less the fee. Review the six-decimal transfer amount, the fee and the two-decimal net credit before sending.
• The fee is shown with the request before you send, and each deposit request keeps the fee it was accepted with: a later tariff change does not alter a request you have already accepted, and deposits credited before this fee was published are not re-charged.
• The provider sets its own charges for funding, conversion and internal transfers. They are separate from the Pepe Pay deposit fee ($1.50 + 5%), and this page does not present them as zero or estimate them in the worked examples.
• Only new own-wallet invoices use the model above. Previously accepted own-wallet requests keep their original verified-USD-reserve credit rules, route, address and accepted fee; they are not migrated to the new route. Historical Spendge invoices and settlement operations remain on hold where their original receipt or settlement cannot be reconciled. A pool balance is not an individual invoice receipt. Contact support about unresolved payments and never pay again.
• Send only the listed asset, on the network the address belongs to. A transfer on the wrong network, or of an unsupported asset, can be lost permanently.

• Moving money from your wallet onto a card costs 2% of the amount credited to the card, charged on top: funding a card with $100.00 debits $102.00 from your wallet — $100.00 onto the card and a $2.00 Pepe Pay fee. The fee is rounded up to the next whole cent.
• The Mini App shows the amount, fee, total debit and tariff before the owner saves a request. A Spendge card request enters an operator queue without wallet debit or reservation. One open request is allowed per card. Your wallet balance may change before execution, and the request does not guarantee card credit.
• The operator explicitly executes the saved quote through the official card API, after funding the issuer separately. An issuer pause, cooldown, reserve shortage, changed tariff or insufficient wallet balance can stop execution. A stale tariff is refused rather than silently repriced. No completion time is guaranteed. Only execution reserves or debits the amount and fee. A definite refusal releases them together; an uncertain result remains held for reconciliation and is never blindly retried or rejected as if it were a refund. A rejected, unsent queued request creates neither a wallet debit nor a refund.
• This is Pepe Pay’ own fee for the transfer. The provider’s charges — section 7 — are separate, and a provider fee already settled is never charged again here.

• External crypto payouts are not available in the current build. No payout route can send to an external address, so a request is refused with an explicit error before any withdrawal is created and nothing is deducted.
• Where a payout route is available, limits apply: $1.00 minimum, $2,000 maximum per request, and $5,000 per 24 hours. These are request rules, not a promise that a payout route exists.
• Where a payout route is available, a withdrawal request is also refused while a card management charge is unpaid, until it is settled.
• No processing time is promised, and no payout date is guaranteed. Where a payout route is available, requests are reviewed before processing.
• For any payout that is processed, the blockchain network fee for the outgoing transfer is set by the network, and you are responsible for the destination address and network you provide; a transfer sent to it is treated as authorised by you.
• Pepe Pay charges no withdrawal fee in the current build. Because no external payout can currently be created, no withdrawal fee can arise.
• Nothing on this page promises that a payout route will be added or gives a completion date for a payout.

The supplied partner transaction-fee schedule is shown below. It is not an account-specific USD quote. Provider charges are separate from the Pepe Pay wallet fees in sections 2 to 5; the provider’s account and balance rules determine where those charges are settled.

Spendge’s published Individual Account rules debit a Card Balance card for the purchase amount, but debit Cards Account for the transaction fee. Maintenance, decline and credit-limit fees are charged to Cards Account regardless of the card’s balance type. These rules do not support a claim that every issuer fee comes out of your card balance.

The provider also applies its 1% card-product fee when its fiat USD balance is moved into the card account. That is an internal funding charge described in section 4, separate from the transaction charges below; this page does not present it as zero.

Scroll horizontally to see all columns.

The supplied schedule states the low-value threshold as EUR 30. The exact USD equivalent and any provider conversion for this account have not been confirmed; no USD threshold is invented here. The blocked-card treatment above is likewise unconfirmed, not a zero charge. Pepe Pay’ conservative internal cost estimates are operator planning assumptions, not confirmed issuer prices or extra fees charged to your wallet. Account-specific terms will be updated here when confirmed.

These cards run on VISA rails with 3-D Secure enabled, and they do not support Apple Pay or Google Pay. The provider also charges the operator for issuing and servicing a card at its own partner rates; those charges are settled between the provider and the operator and are not debited from your wallet on top of the fees above.

Private card details are shown in an authenticated view only, on an explicit request by the card’s owner or by a member with an active team grant. New issuer 3-D Secure codes can also reach the owner’s private bot chat according to the owner’s delivery settings, while a team member reads codes in the app. A revoked grant cannot receive a late credential response; credentials or codes already copied cannot be recalled. Email delivery is currently marked Soon and is not enabled. The privacy policy describes what is and is not kept by Pepe Pay.

Balances, card funding amounts and Pepe Pay fees are recorded in US dollars, and the card product is issued in US dollars. The provider determines the denomination and conversion of its own charges. Any merchant-currency conversion appears in the card’s transaction history as reported by the provider.

This page is the fee list: a change is published here before it takes effect, and fees already paid are unaffected. Each card keeps the versioned tariff it was issued under, so a change applies to cards issued under the new tariff and not to earlier ones. Deposit and funding fees are accepted per operation: a deposit keeps the fee it was accepted with, and wallet-to-card funding is priced per transfer at the rate shown before you confirm it. Nothing already credited or charged is re-priced. Fees are charged as they arise: the issuance fee when a card is created, the management fee on each monthly anniversary, the deposit fee when a deposit is credited, and the funding fee when a card transfer is made. The provider settles its own charges under its account and balance rules.

If you do not recognise a charge, start with the card’s transaction history — a provider transaction charge, a refund charge or a decline charge appears there with the transaction it belongs to. Then tell us through the channel on the contact page. The terms of service describe how reversals and refunds are handled.