Checks for accounts, transactions and funds
Check account access and payment data, transaction authentication and fund handling separately. The operator is Pikabo Technology Co., LIMITED; business registration identifies the entity, not a financial licence, endorsement or fund guarantee.
Data protection
Review collection purposes, retention and access disclosures. Front-end masking does not establish that complete fields are absent from backend storage.
Transaction checks
Investigate card status, available funds, limits, merchant prompts and orders. A transaction record alone does not establish responsibility.
Fund records
Account balance and each card’s funds are managed separately. Check authorizations, settlement, returnable amounts and refund conditions.
Data protection and access permissions
Card number, CVV, expiry and billing details are payment credentials. Consider screen sharing, screenshots, browser extensions and device security; do not send complete credentials through chats, email or public pages.
Visible display
Last-four display helps identification, but does not establish audited database fields, staff permissions or API responses.
Transport and storage
HTTPS protects transport, not backend storage implementation. Public standards such as AES-GCM describe technical requirements, not platform adoption or certification.
Checking access controls
Internal access controls, audit logs and password handling require implementation or audit evidence. A no-password-request practice does not prove all backend controls work.
PCI SSC · PCI DSS · Personal data safety · NIST SP 800-38D · Privacy policy
Transaction authentication and abnormal-activity review
Payments may be affected by merchant requirements, issuer rules, network authentication and platform review. Ordinary spending may be reviewed; frictionless use and successful reviews are not guaranteed.
Before payment
Check accepted card types, issuing regions, billing details, available funds and read-only transaction limits. Funding does not increase those limits.
Authentication prompts
Whether 3DS is requested and whether the segment can complete it are separate conditions. Follow merchant prompts and segment support; ask support when it cannot be completed rather than retrying repeatedly.
Account review
Keep notices, restriction scope and evidence requests and provide genuine purpose and records officially. Restrictions and outcomes follow applicable policies and review; a displayed balance does not prove continuous availability.
Refund Policy · EMVCo · 3-D Secure specification · no-3DS card segment FAQ · AML policy
Account funds, card funds and return conditions
Account balance and card funds are separate operational layers. Separate screens do not establish legal custody, segregated accounts, daily reconciliation or solvency protection. Those arrangements require contracts, institutional disclosures or audit evidence.
Account deposits
Check the USDT token, network, complete address and actual arriving amount on the current deposit page. Transfer success and platform credit are separate states; investigate the original transfer if uncredited.
Card funds
After issuance or funding, check the relevant card’s available funds, authorizations and settled spending. An account balance does not mean the target card has been funded.
Fund returns
Handle card-to-account and account-to-own-wallet returns separately. Fees, cooling periods, settlement and exceptions follow the refund policy; track merchant refunds through the order and merchant process.
Limits of security evidence
Public standards, registration and a successful operation each have limited evidential scope. They do not replace full technical, fund or legal checks.
HTTPS and domains
HTTPS does not rule out phishing. Check the complete domain and avoid login links in unsolicited messages.
Freezing and closure
Freezing does not change an exposed number or cancel subscriptions. Closure is irreversible; check funds, orders and renewals first.
Separate cards and budgets
Separate cards help billing and budgeting, not guaranteed risk isolation, acceptance or independent merchant accounts. Track prior authorizations and catch-up charges.
Protecting accounts and payment details
Protection requires continued checks of devices, email, credentials and orders, not unsupported risk percentages or absolute safety claims.
Login credentials
Use a unique, sufficiently long password, protect the registered email and enable available additional authentication. Do not share one-time codes with support or others.
Devices and screenshots
Keep devices and browsers updated, avoid suspicious extensions and untrusted screen sharing, and retain only troubleshooting fields in screenshots.
Funds and renewals
Budget card funds for actual use and review orders, subscriptions and notices. Cancel unused subscriptions with the merchant and confirm merchant-side rebinding before expiry.
Security checks before use
Record user-verifiable matters separately from those requiring more evidence. Clarify important conditions; a small successful payment is not a complete fund or data safety check.
User-verifiable
Domain, localized policies, fee breakdowns, transaction records, authorization status, card last four digits and official support entry points.
Requires evidence
Institutional identity and authorization, legal fund arrangements, backend permissions, retention implementation, certifications and audits. The interface alone does not establish these matters.
Keep records
Keep the applicable terms version, date, currency and amount and ticket replies. Mask full card numbers, CVV and unrelated identity data in screenshots.
Security reports and follow-up
For suspicious logins, charges or data exposure, protect the account and affected cards, keep records and report officially. Timing and outcomes depend on investigation; no new fixed resolution guarantee is made.
Limit exposure
Stop sharing sensitive data, freeze affected cards, protect email and change potentially exposed login credentials. Freezing does not reverse existing orders or settlement.
Submit facts
Provide time, account identifier, transaction or order number, card last four digits, prompts and checks. Do not submit complete payment credentials, codes or wallet secrets.
Follow-up and disclosure
Follow up in the original ticket. Report security research privately and responsibly; do not disrupt production or obtain others’ data without authorization.