Managing Multiple Virtual Cards
Allocate cards by use, billing cycle or project to reconcile funds and records. Assess the need first, then manage slots, renewals and refunds. Separate cards do not guarantee risk isolation or acceptance.
Benefits and Limits of Multiple Cards
Bill and fund management
Allocate cards by project, purpose or billing cycle to reconcile bills, distribute funds and manage cards individually. One card per merchant is not mandatory. Separate cards or BINs do not guarantee risk isolation, account independence or higher acceptance. Set budgets and spending caps with the merchant; card funds and read-only limits are not advertising budgets.
Add cards for actual needs
One card may be enough for a single stable use with working acceptance. Additional cards should solve a specific recordkeeping or funding need, not serve endless tests or presumed reliability.
Allocation by Use, Project or Cycle
| Dimension | Need | Record |
|---|---|---|
| Use | Separate subscription, advertising or purchasing funds | Merchant, mode and cycle |
| Project | Reconcile different clients or operations | Owner and cost attribution |
| Cycle | Plan monthly or annual renewals | Actual bill and next date |
| Regional requirements | Distinct issuance or authentication needs | Type, region and acceptance |
Account balance and each card’s funds are separate. After an account deposit arrives, fund the intended card before using it. Card balance changes with spending and does not reset monthly. Per-transaction and daily limits are read-only; funding does not raise them.
Choose one primary dimension that maps to bills instead of separating by region, project, merchant and cycle at once. Internal names can describe uses, with last digits for identification. Your labels do not establish platform member approvals or budget permissions.
Slots and Replacement Planning
Standard users can hold up to 5 unclosed cards. Approved advertising users can hold up to 30 after application, not automatically for every team account. Frozen, idle and inactive cards count until closure completes. Idle cards are not automatically closed.
Keep active uses
Prioritize cards with ongoing renewals, purchases or advertising bills.
Review old-card matters
Review idle cards’ bindings, holds, refunds and disputes before closure.
Confirm replacement order
When full, ask support about replacement order rather than closing unfinished uses.
Track the renewal date, payment method and cancellation status in the merchant dashboard. Cancel through the purchase channel. Pikabao sends an expiry reminder one week ahead. Arrange replacement and update the merchant’s payment details; check pending authorizations and refunds before handling the old card. Replacement does not guarantee uninterrupted renewal.
Multiple Merchants on One Card
One card can serve several merchants
A card can serve multiple merchants within its supported scope; there is no universal one- or two-merchant rule. Decide using total bills, renewal dates, privacy and acceptance needs.
Shared funds need combined planning
With shared funds, spending for one purpose may leave too little for another renewal. Separate cards simplify funding management but do not ensure merchant risk controls, issuer restrictions or platform account effects are unrelated.
Team Billing and Credential Protection
Expense attribution
Record project, owner, card digits, merchant and expense attribution. An internal register does not imply Pikabao provides member permissions, approvals or shared card credentials. Check the dashboard for supported collaboration features.
Credentials and slots
Do not place full card numbers, CVVs, passwords or verification codes in shared public sheets or chats. Team use does not automatically qualify for 30 slots; advertising users need approval.
Internal coordination register
Record use, owner, last digits, merchant, cycle, expected bill and reconciliation state. Ownership helps internal queries; it is not permission to forward account passwords or codes.
Your payment details
View full number, CVV, expiry and registered details in your dashboard and use them at trusted checkouts. Update register last digits and merchant details on replacement without accumulating old credentials in public sheets.
Renewals, Records and Costs
Maintain mappings
Maintain digits, purpose, merchant, renewal date, status and remaining funds.
Review funding changes
Reconcile after bills or funding changes and track key expiry dates.
End discontinued uses
End uses with the merchant; check holds, refunds and disputes before closure.
Issuing fees start at $1 and vary by segment, with no monthly or annual fee. Account deposits cost $0; card funding costs 3%. The sending service charges any network or withdrawal fees under its own rules. Review issuance, funded amount, funding fee and account deduction before submitting.
More cards mainly add issuance and administration; they do not reduce the 3% funding fee. Idle cards are not automatically closed; keep or close them according to future uses and unfinished matters.
Choose Cards by Use and Acceptance
Use these product entries to check current segments, fees and authentication, then choose against the merchant’s actual requirements.
Card Types and Uses
Compare uses, fees and acceptanceCheck current networks, segments and authentication.Visa Virtual Cards
Card entry for Visa-accepting merchantsStart with Visa if unsure, but still check merchant acceptance.Mastercard Virtual Cards
Subscriptions, verification and online usesCheck use and authentication; reliability superiority is not guaranteed.US Virtual Cards
When US issuance needs checkingA US BIN is not US residency or guaranteed acceptance or verification exemption.Hong Kong Virtual Cards
When Hong Kong issuance needs checkingUse registered details and merchant rules, not as a substitute for real account information.Each additional card incurs its segment’s issuing fee. If your current card meets the use, another card is not needed merely for testing.
FAQ
When are several cards useful?
Allocate cards by project, purpose or billing cycle to reconcile bills, distribute funds and manage cards individually. One card per merchant is not mandatory. Separate cards or BINs do not guarantee risk isolation, account independence or higher acceptance. Set budgets and spending caps with the merchant; card funds and read-only limits are not advertising budgets.
Must a card have only one merchant?
No. Decide using supported scope, total bills, cycles and recordkeeping. Separate cards help manage funds but do not guarantee risk isolation or better acceptance.
What if 5 unclosed cards are not enough?
Standard users can hold up to 5 unclosed cards. Approved advertising users can hold up to 30 after application, not automatically for every team account. Frozen, idle and inactive cards count until closure completes. Idle cards are not automatically closed.
Can separate cards raise transaction limits?
Account balance and each card’s funds are separate. After an account deposit arrives, fund the intended card before using it. Card balance changes with spending and does not reset monthly. Per-transaction and daily limits are read-only; funding does not raise them.
What should a team card register contain?
Record last digits, purpose, merchant, owner, renewal date and funds status, not full numbers, CVVs, passwords or codes. A register is not a platform member-permission feature.
Do separate cards lower funding fees?
No. The 3% proportional funding fee remains, while additional cards incur issuance fees. Issue for actual uses and check unfinished matters before handling idle cards.
Does freezing an idle card free a slot?
No. Frozen, idle and inactive cards count as unclosed until closure completes. Review merchant bindings, holds, refunds and disputes first. Idle cards are not automatically closed.
Check Uses and Fees Before Issuing a Pikabao Card
Register and complete required checks, review current segments, merchant requirements and actual fees, then fund the intended card for its bills.