01
Business creates users
Manage only your own users from Portal or API.
CORPORATE PAYOUT INFRASTRUCTURE
Understand your funding.
Understand your funding.
Use it with clarity.
V-REC is a B2B2C platform that separately tracks corporate payouts and direct tenant allocations while connecting onboarding, KYC, cards and transaction history. Businesses can manage their own V-REC users through the Merchant Portal or API.
✓ Merchant-scoped data
✓ KYC required
✓ API + Portal
BUSINESSMerchant Portal / APIUsers · KYC · Controls
VV-RECCorporate Payout Platform
USERReceive · SpendApproved payouts only
APIHMAC
KYCVerified
LedgerSource tracked
02
KYC verification
Identity verification gates card and withdrawal features.
03
Receive corporate payouts and tenant funding
Records confirmed payouts and tenant allocations separately.
04
Use supported cards
Use eligible V-REC value through supported card rails.
TWO CLEAR EXPERIENCES
One platform, two clear experiences
Businesses get operational tools and APIs. Users get a clear payout and card experience. Roles remain intentionally separated.
Embed V-REC into your service
Keep users isolated by Merchant ID and provision, verify or suspend them from your own backend.
- Merchant Portal
- HMAC Merchant API
- Merchant-owned users only
- Credential rotation and revoke
Receive and use approved payouts
Users can view beneficiary identity, payouts, tenant allocations, KYC, cards and history by original source. Self-funding and V-PAY transfers into V-REC USD source value are not supported. The SAKURA crypto wallet is separate.
- Payout & funding history
- KYC status
- Virtual / Physical Card
- ATM from eligible value
MERCHANT API
Integrate V-REC from your existing system
No tenant subdomain is required. Merchant API credentials establish ownership server-side; client-supplied merchant IDs are not trusted for authorization.
HMAC-SHA256Idempotency-KeyNonceIP Whitelist
{
"email": "[email protected]",
"first_name": "Taro",
"last_name": "Yamada",
"country_code": "JP",
"dial_code": "+81",
"phone": "9012345678"
}201 Created · activation_url returned
TRACEABLE ACTIVITY
See each financial source clearly
A tenant allocation is not a corporate payout. Card spending and crypto purchases also have independent records.
Payouts & tenant allocations
Separate corporate payouts, direct allocations and returns in the V-REC USD source ledger.
Card purchases & ATM
Retrieve issuer statements via SAKURA and keep them separate from internal card records.
USDT & custom tokens
Report transfer amounts, tokens paid and SGP-USD or points delivered in their respective units; never auto-net them into USD.
CONTROL BY DESIGN
Control the source, not only the balance
V-REC does not treat a shared issuer balance as interchangeable value. Authorization decisions are based on source-attributed V-REC ledger value.
Personal bank/card funding does not create V-REC USD source value. The crypto wallet is separate.
V-PAY value cannot become V-REC ATM-eligible value.
An API instruction alone never credits withdrawable value.
Each merchant can manage only its own V-REC users.
GET STARTED
A simple path to business integration
- 1Create a V-REC Merchant
Platform admin links the business to its SAKURA Merchant relationship.
- 2Sign in to Merchant Portal
Create users or issue server credentials from the portal.
- 3Connect the Merchant API
Use signed HMAC requests from your existing backend.
- 4Launch to users
Deliver activation, KYC, payout and card experiences end-to-end.
V-REC ACCESS
Are you integrating V-REC or using it?
Access is separated by role: platform administrators, business merchants and end users use different sign-in flows.