Terms of service

These terms are an agreement between you and the operator of Pepe Pay (“Pepe Pay”, “we”). They cover the Telegram bot at pepepayapp, the Mini App, and the public pages on this website. By creating an account or using any of them, you accept these terms.

Pepe Pay is software for managing virtual payment cards. Cards are issued by external card providers. Pepe Pay does not present itself as a bank, a card issuer or a licensed financial institution, and it makes no claim of any licence, registration or regulatory approval. Balances it records are internal ledger entries, not bank deposits. The cards themselves are governed by the issuing provider’s own terms and by the rules of the card networks, which apply in addition to these terms.

The operator’s legal identity, registered address and governing law are not published, because they have not been verified. Pepe Pay is not naming an unverified entity or jurisdiction — see the contact page. Nothing below replaces verified operator details.

• You need a Telegram account. That account is how you sign in and how Pepe Pay identifies you (numeric Telegram ID, first and last name, and username where you have one).
• You must be able to enter into a binding contract where you live — in most jurisdictions that means you are at least 18 years old.
• You are responsible for your Telegram account and for everything done through it. Keep it secure; do not share your Telegram account or Pepe Pay sign-in with anyone. This does not stop a card owner from granting in-app card access through Teams, which never shares an account.
• A team member must also be able to enter into a binding contract and must follow these terms. Adding someone to a team requires that they sign in to Pepe Pay, either before the owner adds their account or through a single-use invitation link. It does not create a provider account or transfer card ownership. Treat an invitation link as a key: give it only to the intended person and revoke it if it may have leaked.
• Provide accurate information, do not impersonate anyone, and do not open accounts to evade a restriction, limit or closure.
• We may suspend or close an account that breaches these terms, the acceptable use policy, or the provider’s rules.

Pepe Pay:

• keeps a balance and records card spending, fees, and — where those features are available — deposits and withdrawal requests;
• passes your card requests to the card provider and shows you the provider’s result;
• offers one card product in the current build: Services & Advertising, a USD card for digital services and legitimate advertising, issued by the provider under a fixed list of permitted merchant categories;
• fetches private card details from the provider and shows them in the Mini App only on an explicit request by the card’s owner or by a member with an active team grant;
• notifies the card’s owner of new issuer 3-D Secure messages in the app and attempts private delivery through the bot according to the owner’s Profile settings. A team member reads 3DS codes in the app while the grant is active and does not receive the owner’s automatic notifications. Email delivery is currently marked Soon and is not enabled. Delivery and the issuer’s continued acceptance of a code are not guaranteed;
• shows card statuses and transaction history as reported by the provider, lets you freeze a card — a provider block that may not be reversible — and lets you request the end of our paid management service for that card. Unfreezing and closing a card are available only where the issuing provider supports them; ending the paid service never blocks or closes the issuer card automatically.
• lets an owner share an owned card with other Pepe Pay accounts through Teams. While the grant is active, a member can see the shared card’s balance, status, limits and card activity, open its credentials, static 3-D Secure password and 3DS codes inside Pepe Pay, and pay with it. The owner keeps ownership of the card and of the wallet and card balances, and remains responsible for funding, fees, card controls, billing and the paid-service exit. Removing a member, revoking a card, or deleting or leaving a team ends future access through that team only; access through another team may remain, and credentials or codes already copied cannot be recalled.

Pepe Pay does not:

• issue cards, or decide whether a card is approved;
• hold your balance in a bank deposit account, or pay interest on it;
• decide whether a merchant, service or advertising platform accepts a card;
• support mobile wallets: the offered cards cannot be provisioned into Apple Pay or Google Pay;
• move ownership of a card or make a team member the card’s owner of record; a Teams grant changes who can view and use a card, not who owns it;
• run its own identity-verification programme, or claim that the provider has verified every Pepe Pay account holder. Where the provider asks for identity information or documents, they are supplied to the provider for its own checks; a Teams membership does not create a provider account or transfer any provider verification.

The fees Pepe Pay charges are listed on the fees page. Card issuance costs $5.00 per card and includes the card’s first month of management. From the second month, management costs $3.00 per calendar month and falls due on the card’s monthly anniversary counted in UTC. The issuance amount is reserved before the issuance request is sent and charged only after confirmed issuance; a definite rejection releases the reservation, and an uncertain provider result remains held until reconciled.

The management fee is charged from the card owner’s wallet balance, and that balance is never overdrawn. If the balance does not cover a month, that month stays unpaid and overdue, the amount is caught up when the balance allows, and 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. Nothing is frozen automatically, because the provider’s documented API cannot undo a freeze; a frozen card keeps accruing the fee under this tariff — a Pepe Pay charge of its own, not a pass-through of any provider charge — and closing a card, where the provider supports closing, cancels future and unpaid periods. Each card keeps the versioned tariff it was issued under, and cards created before this tariff was published are not enrolled in it.

You may request the end of Pepe Pay’ paid management service for a card in the app. Pepe Pay does not block or close the issuer card automatically, and ending the paid service is not an issuer closure. A block happens only if the request separately opts in to it. With the provider available in the current build there is no close operation, so an exit can complete only if the request opted in to blocking the card. Monthly fees continue on the usual anniversary while the request is pending. It 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, does not refund a paid period, and does not enrol the card again. A completed exit cannot be cancelled. If the request opted in to blocking the card, that uses the provider’s block operation and cannot be undone in the app where the provider has no unblock operation. Any balance left on the issuer card is recorded for operator follow-up and is not automatically returned or credited to your wallet by ending the paid service. 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 a card, change its controls, manage its billing or request an exit; a team member cannot.

Pepe Pay may send at most one proactive Telegram reminder per billing period (amount, UTC due date and masked card suffix, never card credentials or codes). Delivery is best-effort and is not retried after a failed or unconfirmed send, so a missing reminder does not change what is owed; the billing state in the app is the durable record.

The provider sets its own per-payment, refund and specified-decline charges. Its account and balance rules determine where those charges are settled; they are not necessarily deducted from the card’s balance. The available supplier schedule is disclosed on the fees page, separately from Pepe Pay’ own fees. Provider amounts there are supplied or preview figures, not account-confirmed prices, and an unknown amount is not shown as zero. Network fees for sending or receiving crypto are paid to the blockchain network, not to Pepe Pay. A fee not listed on the fees page is not charged by Pepe Pay.

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. Funding a card from your wallet costs 2% of the amount credited to the card, charged on top: funding a card with $100.00 debits $102.00 from your wallet. The percentage parts are rounded up to the next whole cent and the $1.50 deposit part is fixed; both are shown before you confirm the request. A deposit keeps the fee it was accepted with. Card-funding requests store the accepted amount, fee, total and tariff; a stale tariff is refused at execution rather than silently repriced. The provider sets its own costs for card-account liquidity, conversion and internal transfers; they are separate from the Pepe Pay fees above, and this page does not present them as zero or estimate them. The offered cards do not support Apple Pay or Google Pay.

Every card request is subject to the provider’s approval. The provider may decline a request, ask for identity documents, set or change limits, or refuse to issue a card to a particular person or for a particular purpose.

Pepe Pay does not guarantee that a card request is approved, that a card keeps working, or that any merchant or platform accepts a card. A definite rejection means that no card is issued and the issuance fee reservation is released.

Cards are issued for digital services and legitimate advertising, inside the provider’s permitted merchant categories, which are listed on the acceptable use page. A payment in a category the provider does not permit is declined by the bank, and Pepe Pay cannot make it go through. Sharing a card through Teams does not change provider approval, the card’s limits or whether a merchant accepts it.

• New deposits use automatic Pepe Pay own-wallet USDT-TRC20 invoices where the receiving wallet is configured. These are not Spendge invoices. Create a request in your account and use only its exact amount, address, network and payment window. A payer name is not required. Never reuse a historical invoice or receiving address for a new payment.
• Existing balances, accepted fees and payment identities are preserved. Cabinet sessions, password login and browser automation are not used. Unresolved invoice receipts and settlement operations require support and are not silently marked complete or converted to another route. Do not pay an already-paid request again.
• Balances are held in US dollars, in cents. A deposit is credited at one dollar per token, without a market exchange-rate calculation, less the Pepe Pay deposit fee ($1.50 + 5%) deducted from the amount: a $100.00 base deposit credits $93.50. The minimum base deposit is $50.00. The accepted fee is recorded with the request and shown before payment, and earlier deposits keep their accepted terms. Own-wallet invoices add a small identification fraction to the exact transfer amount; it is not credited and carries no fee. Historical customer-paid Spendge invoices had no identification fraction. Blockchain network fees are separate.
• For new own-wallet invoices, detection alone is not a completed credit. The exact transfer must pass canonical blockchain receipt verification and finality; the accepted net amount is then credited automatically to your internal USD wallet, backed by USDT received in the Pepe Pay wallet. This does not verify issuer USD reserve, and no funds are transferred to Spendge automatically. The operator funds the issuer separately. No completion time is guaranteed. Previously accepted routes are not migrated: their original verified-USD-reserve, invoice-receipt and settlement requirements remain in force. Unsupported or uncertain reconciliation stays on hold for operator resolution. A pool movement is not an individual invoice receipt. Do not pay an already-paid request again. Sending an unsupported asset or using the wrong network can result in lost funds; recovery is not guaranteed.
• New own-wallet payments are received into the operator’s crypto wallet. Historical invoice payments were received by Spendge for the operator’s issuer account. Your Pepe Pay balance is an internal USD record, not a personal Spendge account or bank deposit: it earns no interest, has no deposit-guarantee coverage, and gives no claim on a particular wallet, address or bank account.
• A balance is a record of funds held to pay for the service and to fund cards; withdrawals, where available, are made from it.
• Funding a Spendge card requires a request by its owner and explicit operator execution through the official card API. Saving a request does not debit or reserve the wallet and does not fund the card. One open request is allowed per card. The accepted amount and fee are debited or reserved only when the operator executes it, subject to the wallet balance and issuer availability at that time. Pauses, cooldowns, insufficient issuer reserve or a changed tariff can prevent execution; no completion time is promised. An uncertain dispatched operation must be reconciled and is not blindly resent or rejected. Rejecting an unsent request creates no wallet debit or refund. Saved request statuses remain visible in the app.
• If a balance is credited in error, we may correct it after telling you what happened.

• External crypto payouts are not available in the current build. No payout route available to this build can send funds to an external address, so a withdrawal request is refused with an explicit error before any request is created and without deducting anything.
• Where a payout route is available, withdrawals are requests: you provide an amount, an asset and a destination address, and the request is reviewed before it is processed.
• Where a payout route is available, these request limits apply: a $1.00 minimum, a maximum of $2,000 per request, and $5,000 within 24 hours.
• A withdrawal request would also be refused while a card management charge is unpaid, as described in section 4, and, where a payout route is available, would be available again once the charge is settled.
• No processing time is promised. Where a payout route is available, requests can be delayed by review, network conditions or provider action.
• For any payout that is processed, you are responsible for the destination address and network. A withdrawal sent to an address you specified is treated as authorised by you.
• Network fees are paid to the network. Pepe Pay does not charge a withdrawal fee in the current build; because external payouts are unavailable, no withdrawal fee can currently arise.
• Nothing in this section promises that a payout route will be added or gives a completion date for a payout.

Refunds, reversals and chargebacks follow the card network’s and the provider’s rules — not Pepe Pay’ preferences. When a reversal or refund reaches the service, the corresponding entry appears in the card’s transaction history, and the balance is adjusted according to the provider’s report.

Reversals are not instant. Where the provider or the card network does not return funds automatically, a reversal or refund has to be settled manually with the provider through a support channel. Pepe Pay does not offer instant cash-out of a card balance, and a card balance is not an account you can draw down at will.

On a card shared through Teams, refunds, reversals and chargebacks affect the owner’s card and wallet records as reported by the provider; they do not create a balance in a member’s wallet. The owner remains responsible for those outcomes.

Pepe Pay does not control those timelines and does not promise a date for money that a merchant, an acquirer or a card network has not yet returned. If a refund does not appear, start with the merchant, and tell us through the channel on the contact page so we can check what the provider reports.

Your use of the service is limited by the acceptable use policy, which is part of these terms. It lists prohibited purposes and what happens when the policy is broken, including suspension or closure of an account.

Features may be changed or suspended for maintenance, security or legal reasons. New Spendge deposits are disabled because the published API-key contract does not support invoice creation and Fiat-to-Card settlement. Existing balances and payment records are preserved. No external crypto payout route is configured, so new withdrawal requests are refused. We do not publish an uptime guarantee.

• The service is provided as it is. Pepe Pay does not promise that it is uninterrupted, error-free, or fit for a particular purpose, and does not promise that a card will be approved or accepted.
• To the extent the law allows, Pepe Pay is not liable for indirect or consequential losses, lost profits, or losses caused by the card provider, a card network, a merchant, a blockchain network or your own mistakes (for example, an address or network used incorrectly).
• Nothing in these terms excludes liability that cannot lawfully be excluded, and nothing here limits rights you have under mandatory consumer law.
• You are responsible for complying with the law where you live, including tax obligations that arise from your use of the service.

These terms are versioned and dated at the top of the page. We will announce material changes in the Telegram bot before they take effect. Continuing to use the service after that means you accept the updated terms; if you do not accept them, stop using the service and, where an external payout route is available, take out any balance through the withdrawal process.

The governing law and the place where disputes are handled are not published, because they have not been verified. They are not set in this version, and Pepe Pay does not name a jurisdiction that has not been confirmed.

Questions about these terms go to the channel listed on the contact page.