For suppliers
I am buying, and I would rather buy it all from you
Papaweba is Levin Ronskii, a registered sole proprietor (個人事業主) in Kitakyushu, Japan. I buy digital gift-card codes and sell them to retail buyers on two Russian marketplaces under the brand DIGITY. The storefronts opened in September 2026. Spend is roughly $10,000 a month and I expect it to triple by the end of 2026. Today it is split across six sourcing accounts. I want one supplier instead.
01What I need
Ordered by how much it matters to me, not by how much of it you might carry.
- Apple Gift Card, United States — $2 to $500, the full denomination ladder. This is the priority. I currently list 26 US denominations and the small ones move as fast as the large ones, so a supplier who only carries $25/$50/$100 solves about a third of the problem.
- Apple Gift Card — Turkey (₺10–₺2,000), Russia (₽500–₽9,000), India (₹100–₹10,000). Secondary, but all three are live and selling.
- Roblox gift cards and Robux credit — 50 to 24,000 Robux, global and region-free. RU-issued stock where it exists.
Instant or near-instant issue matters more than the last half a percent of margin: a buyer on a marketplace is waiting and the platform is counting the minutes. A supplier who delivers reliably in seconds is worth more to me than one who is slightly cheaper and sometimes takes an hour.
02Volume
- Now: ≈ $10,000 a month in purchases (≈ $2,500 a week).
- Target by December 2026: ≈ $30,000 a month.
- Basis: 572 retail orders in the first ten days of trading, 13–22 September 2026, from a standing start with two storefronts opened this month.
- Mix: Apple is the majority of spend; Apple US alone is the largest single line.
Those are counted numbers from my own order database, not projections dressed up as history. The growth figure is the one thing on this page that is a forecast, and it is a forecast built on ten days of real demand rather than on a spreadsheet.
03How I settle
- USDT or USDC — preferred, and how I fund most accounts today. Any mainstream network.
- USD bank wire from my own account, in my own name. I am not funded by third parties and there are no payment agents in the chain.
- Prepaid balance rather than credit terms. I would rather keep a float with you than ask for an invoice line. If you prefer net terms after a qualification period, that is fine too, but I am not asking for them up front.
04Integration
- Per-order REST API is what I want. I already run against several: purchase request with an idempotency key, code returned in the response or on a short poll, balance and stock endpoints for the catalogue sync. If yours works that way, I can be live on it quickly.
- Batch delivery — CSV or encrypted file drops against purchase orders — is workable and I will build for it. It costs me stock-holding and it slows the catalogue, but it is not a blocker.
- What I need from the API besides the code: per-item cost at time of purchase, a stable order reference, and a stock or availability signal. Pricing that changes without a queryable endpoint is the main thing that breaks a marketplace listing.
05What you get from me
The fraud question is the one that actually decides these conversations, so it is answered in full on a page of its own: code handling and fraud controls. The short version:
- Codes are encrypted with AES-256-GCM before storage, fingerprinted with SHA-256, and issued exactly once to the paid marketplace order that bought them.
- Sales are retail only, to individual consumers, through platforms that verify sellers, hold the payment and keep their own order record. No onward resale, no bulk B2B, no off-platform sales. There is no checkout on this website.
- No second-hand stock. Nothing enters the system that did not come from a supplier API against an invoice.
- Every purchase is reconciled into a Japanese tax return, so the code ledger and the books are the same data.
06Verification
Under an NDA, and on request, I will provide:
- Japanese sole-proprietor registration (開業届, filed 10 January 2026) and tax-office details — 門司税務署, Kitakyushu.
- Russian sole-proprietorship registration for the retail entity — ИНН 366227464117, ОГРНИП 326508100539173, already public on the marketplace storefront.
- Marketplace seller-account confirmation for both storefronts.
- Existing supplier account confirmations and purchase history with invoices.
- A live walk-through of the order pipeline, from marketplace order to code issue.
- Identity documents where your onboarding requires them.
The storefronts are the part you can check right now, without asking me anything: Wildberries and Yandex Market. Both show my registration details, my listings and my buyers' complaints.
07What I am not asking for
- Not asking for credit. Prepaid is fine.
- Not asking for exclusivity, a reseller title, or use of your brand in my marketing.
- Not asking you to onboard a company structure that does not exist — it is one person, and the paperwork says so.
- Not asking for wholesale lots to move on: the codes end at a consumer.
08Getting in touch
Mail [email protected] or [email protected], or use the form on the front page with the topic set to “I can supply codes”. I am in JST (UTC+9) and I answer in English, Russian or Japanese.
Useful things to include: brands and regions you carry, the denomination ladder for Apple US, whether issue is instant, how the API authenticates, how balances are funded, and your minimum volume. If I am below your minimum today, say so — I would rather hear it now and come back in a quarter with the numbers.
If you are on the other side of this and you are reviewing me as an applicant: every claim on this site is deliberately checkable. The storefronts are live, the registrations are real and public, the numbers come from an order database, and I will answer any question you send to [email protected] in writing.