CHANGELOG

Changelog: product, policy, and content updates

Changelog records, on a timeline, every product launch, rule change and content update from PIKABAO (the former "platform announcements" now live here), stating for each entry when, what keyword and what changed. The timeline runs from the bottom up: the 2023 start sits at the bottom, and the newest entry sits at the top.

AuthorPIKABAO Data Research GroupLast reviewedUpdates8 entriesStart2023 Q2-Q4 · Brand site live

The timeline builds upward: the start 2023 Q2-Q4 · Brand site live sits at the bottom, then the team workspace, regional BINs, scenario-based card selection, narrowed deposit networks and scenario tutorials, with the newest entry Sep 2026 · Refund freeze and release applications at the top — Jump to the start ↓

Key takeaways
  • The 8 entries cover the 2023 Q2-Q4 brand launch through the September 2026 refund-freeze rule;
  • Three card types (Visa / Mastercard / US BIN) and five issuing regions are two independent dimensions for choosing a card;
  • Merchant refunded amounts are frozen for 90 days under the standing risk-control rule; refunds from normal consumption can apply for expedited release with three pieces of evidence;
  • Fee changes aren't retroactive: balances already deposited and cards already opened follow the terms in force at the time.

Update timeline

Refund freezeLatest
The freeze on merchant refunded amounts and applying for release

The risk-control rule states clearly: merchant refunded amounts are frozen for 90 days, counted from the day the refund is credited, and released automatically on expiry with no extra application needed. The freeze applies only to that refunded amount — the rest of your balance is unaffected, and you can keep opening cards and spending.

If the refund comes from normal consumption and your account has a low refund frequency, you can provide evidence and the platform will assist in applying to the risk-control department for expedited review and early release; the outcome is subject to review. Three items are needed: the merchant refund voucher (clearly showing the merchant name, refunded amount and successful-refund status), your PIKABAO ID, and the amount to release (matching the voucher). The flow: submit a ticket in your account with the three items attached (fund tickets have the pipeline examined within 90 minutes; never send screenshots or card numbers in any private chat) → wait for the risk-control review, up to 72 hours, with the conclusion delivered by ticket → approved means early release; not approved simply means the 90-day freeze runs to expiry.

Three different "freezes" — don't mix them up: the 90-day freeze on merchant refunded amounts applies to refunds credited to you; the 60-90 day upstream settlement freeze on card closure applies to money recovered when you close an account; the 24-hour withdrawal safety cooldown applies to outgoing funds. They cover different things, run on different clocks and don't stack.
Scenario tutorials
AI subscription, ad-spend and streaming subscription tutorials went live

Subscription tutorials went live as a coherent set by scenario: AI subscriptions cover subscribing, renewing and card-binding terms for ChatGPT, Claude and other mainstream AI tools; ad spend covers card binding, pre-authorization holds and charge cadence for Google Ads, Meta Ads and similar accounts; streaming subscriptions cover Netflix, Spotify, Apple Music and other platforms that decide content by region and time zone. Each article quotes the official wording first and then explains the practical boundaries; prices are labeled with the capture date and defer to the official pricing pages of the current version.

Deposit networks
Deposit networks narrowed to USDT: TRC20 and ERC20 only; dedicated addresses stable long-term

Account deposits run only on the TRC20 and ERC20 networks of USDT; assets sent over other networks (BEP20, for instance) can't be credited and can't be recovered along the original path. Every account has a dedicated deposit address that stays valid long-term — it doesn't expire, so you can save it and reuse it. The reason for narrowing is straightforward: while several networks were supported, the cost of failed credits and reconciliation fell almost entirely on the user; with two networks left, there is only one thing to check when something goes wrong — whether you used one of these two.

US BINs
Additional US-region card BINs added

A new batch of US-region card BINs was added, widening what you can choose from. The new ranges are genuine US BINs like the existing ones, meant for cases that explicitly require a US issuing country — switching an Apple ID to the US store, or Netflix US. Expanding the ranges also reduces the knock-on effect when a single BIN range gets flagged by a merchant's risk control.

Scenario-based selection
Product update v1.1: more interface features, cards selectable by payment scenario

The product moved to v1.1 with interface and feature improvements, adding card selection by payment scenario: pick the scenario first (AI subscriptions / ad spend / streaming / app stores / e-commerce), and the page recommends the card type and issuing region for it and flags the most common failure reasons in that scenario. You no longer have to cross-reference a table to decide which card type goes with which region.

Regional BINs
Hong Kong, Japan and Singapore local BINs opened

Local BIN ranges opened in Hong Kong (China), Japan and Singapore, extending issuing regions to five alongside the existing US and European ranges. Local BINs solve the "the platform judges you by issuing country" class of problem: Japanese platforms require a JP BIN, and some Hong Kong and Southeast Asian platforms accept only their own region's BINs — US cards used to be rejected right there. When choosing a card, just ask whether the platform checks the card network or the issuing country.

Team workspace
Team workspace live: team management, member limits and centralized funds

The team workspace went live for multi-person use: one main account can hold several members, with cards and spending limits assigned per person; top-ups go into the main account and the administrator allocates and reclaims them, so nobody has to top up individually; each member's spending is visible per person, and cards and limits can be reclaimed immediately when someone leaves. It suits small teams sharing a budget for ad spend, or subscribing to several AI tools at once.

Brand liveStart
Brand site live: Visa, Mastercard and US BIN card types fully presented

The PIKABAO brand site went live with all three card types — Visa, Mastercard and US BIN — available from the first release, selectable by card network and issuing region when you open a card. The operating entity completed its Hong Kong (China) registration, with the entity name, business registration number and registered address verifiable independently on the compliance page; in the same period, cooperation with upstream licensed card issuers kept expanding, leaving the channel open for opening BIN ranges by region later on.

How the capabilities were built, 2023-2026

When the brand site went live in 2023, the Visa, Mastercard and US BIN card types were all in place at once, the operating entity completed its Hong Kong (China) registration, and cooperation with upstream licensed issuers was being laid down in parallel. In 2024 the team workspace went live, letting one account assign cards and limits to several members. From early to late 2025, local BIN ranges opened for Hong Kong (China), Japan and Singapore; in August the product moved to v1.1 with card selection by payment scenario; in October another batch of US BINs was added. In April 2026 deposit networks narrowed to USDT on TRC20 and ERC20; in May the AI-subscription, ad-spend and streaming tutorials went live as a set; and in September the freeze on merchant refunded amounts and how to apply for release were written up as a three-step flow.

When choosing a card, separate the two dimensions first: card type is the network (Visa / Mastercard), region is the issuing country (United States, Hong Kong (China), Japan, Singapore, Europe) — fix whichever one the platform checks.

Two terms for fee and rule changes

  1. The current wording is what appears on Changelog and in the respective terms pages: support private chats, community screenshots and third-party retellings don't count.
  2. Fee changes aren't retroactive: balances already deposited and cards already opened follow the terms in force at the time; new terms govern only later actions.

Rules clear — now open a card

Run the full flow with a minimum amount before deciding how much to invest.

Historical records and current rules

The changelog records what was published at the time, not a replacement for current policy. For fees, reviews and refunds, check the record date, operation date and corresponding policy together.

01

Publication date

Historical titles and text remain for traceability; old technical descriptions and service deadlines are not proof of current implementation.

02

Applicable version

Compare versions and effective dates in the terms, refund policy and pricing. Check existing operations against their announcement and applicable terms, not only the latest entry.

03

Resolving differences

If deadlines or fund handling differ between the log and policy, keep both links and the operation record for support rather than relying on a more favorable verbal claim.

Tracking subscription and fee changes

Product availability and guide publication do not guarantee merchant acceptance. Rule updates do not automatically change merchant-saved payment details.

01

Keep the original order

Keep the fee breakdown, date and order number for issuance, funding or subscription to check applicability before and after a change.

02

Check the next renewal

Check merchant price, taxes, card expiry and renewal date separately. Cancel subscriptions with the merchant; emptying or freezing a card is not cancellation.

03

Act after checking

Ask official support when important conditions remain unclear. A successful historical payment does not establish acceptance after an update or at renewal.

Refund policy → Card balance refunds · full rules
Online support