Dashboard Role: Token User

The Token User role allows users to create and manage payment tokens through the Connected Payments dashboard.

What You Can Do

Create Tokens

Create Tokens

• Create tokens via Virtual Terminal
• Store card information securely
• Add custom metadata
• Validate card details
• Generate token receipts

Manage Tokens

Manage Tokens

• View token history
• Update token metadata
• Update expiry dates
• Delete tokens
• Search and filter tokens

Process Payments

Process Payments

• Process token-based payments
• Use tokens for purchases
• Use tokens for pre-authorisations
• Generate token reports
• Download token data as CSV

Permissions

Permission	Description
Create tokens	Create tokens via Virtual Terminal
Store card information	Securely store card details in secure compliant silos
Process token payments	Use tokens for payment transactions
Update tokens	Modify token metadata and expiry dates
Delete tokens	Permanently remove tokens from system
View token history	Access complete token history
Generate reports	Create and download token reports

Token Storage

Secure Compliant Storage

Tokens securely store sensitive cardholder data in compliance with industry security standards.

What's Stored:

Data	Format
Masked PAN	e.g., 4111 11XX XXXX 1111
Cardholder Name	Full name on card
Expiry Date	MM/YY format
Card Type	Visa, Mastercard, Amex, etc.
Custom Metadata	Customer ID, references, etc.

What's NOT Stored:

• CVV/CVN codes
• Full card numbers (only masked)
• PIN numbers

Security Features:

• Sensitive data encrypted
• Stored in secure token silos
• Cryptographically isolated
• Industry-standard security

Token Terminology

Token Silo

Token Silo

Cryptographically isolated storage unique to your merchant account.

Shared Silo (Default):

ACME (Parent) - Token Silo: MAIN
├── ACME\ONLINE - Uses MAIN silo
├── ACME\RETAIL - Uses MAIN silo
└── ACME\WHOLESALE - Uses MAIN silo

• Top-level silo shared by sub-divisions
• Token created in ONLINE usable by RETAIL
• Convenient for multi-division businesses

Separate Silos (Optional):

ACME (Parent) - Token Silo: MAIN
├── ACME\ONLINE - Token Silo: ONLINE_SILO
├── ACME\RETAIL - Token Silo: MAIN
└── ACME\WHOLESALE - Token Silo: MAIN

• ONLINE has separate silo
• Tokens in ONLINE_SILO not usable by RETAIL
• Useful for data isolation requirements

To set up separate silos: Contact your account manager

Token Format

Token Format

How card numbers are restructured for security.

Example:

Original card: 4111 1111 1111 1111
Token format:  4111 11AB CDEF 1111

• First 6 and last 4 digits preserved
• Middle digits replaced with random characters
• Maintains card type identification

Available Formats:

Format	Example	Description
F2L4F	41XX XXXX XXXX 1111	First 2, Last 4, Fill
F6L4F	4111 11XX XXXX 1111	First 6, Last 4, Fill
F2L4AN	41AB CDEF GHIJ 1111	First 2, Last 4, Alphanumeric
F6L4AN	4111 11AB CDEF 1111	First 6, Last 4, Alphanumeric
F2L4A	41AB CDEF GHIJ 1111	First 2, Last 4, Alpha
F6L4A	4111 11AB CDEF 1111	First 6, Last 4, Alpha
13N	1234567890123	13 Numeric digits
16N	1234567890123456	16 Numeric digits
ALPHANUMERIC08	ABC12345	8 Alphanumeric characters

Note: Token format is set at hierarchy level and cannot be changed per token. Contact your account manager to confirm your format.

Creating Tokens

Accessing the Virtual Terminal

Virtual Terminal URL: https://connectedpayments.commbank.com.au/payment/dashboard/home

1. Navigate to Virtual Terminal URL
2. Enter your credentials
3. Click Log In
4. Click Terminal in left sidebar
5. Select Create Token option

Token Creation Steps

Step 1: Enter Card Details

Required Fields:

Field	Description
Card Number	Full card number
Cardholder Name	Name on card
Expiry Date	MM/YY format
CVV	For validation only (not stored)

Optional Fields:

Field	Description
Customer ID	Internal customer reference
Receipt Number	Transaction reference
Internal Reference	Custom tracking information
Custom Metadata	Business-specific data

info

Each hierarchy may have different required fields. Contact your account manager to customise.

Step 2: Review Details

1. Confirmation page displays
2. Verify all information
3. Check masked PAN format
4. Confirm metadata

Step 3: Create Token

1. Click Create Token
2. Token generated
3. Receipt page displays
4. Token value provided

Token Receipt

Receipt Shows:

• Token value (e.g., 4111 11AB CDEF 1111)
• Masked PAN
• Cardholder name
• Expiry date
• Card type
• Creation timestamp
• Metadata

Managing Tokens

Viewing Tokens

Navigate to Tokens:

1. Log in to Connected Payments dashboard
2. Click Tokens tab in left sidebar
3. View all active tokens

Token List

Available Information:

Field	Description
Token Value	Masked token value
Cardholder Name	Name on card
Expiry Date	Card expiry date
Card Type	Visa, Mastercard, Amex, etc.
Creation Date	When token was created
Metadata	Custom fields and references
Actions	Update/Delete options

Filter Options

Filter	Options
Date Range	Today, Last 7/30 days, All time, Custom
Card Type	Visa, Mastercard, Amex, etc.
Expiry Status	Active, Expired
Search	Search by metadata

Updating Tokens

Update Process

1. Navigate to Tokens page
2. Find token in list
3. Click Update button
4. Modify editable fields
5. Click Save

Editable Fields

Field	Can Edit
Cardholder Name	Yes
Expiry Date	Yes
Metadata Fields	Yes
Custom References	Yes
Token Value	No
Card Number	No
Card Type	No
Token Silo	No
Creation Date	No

Common Update Use Cases

Update Expiry

Update expiry date when card renewed:

1. Customer receives new card
2. Locate token in system
3. Update expiry date
4. Save changes
5. Confirm update successful

Correct Name

Correct cardholder name spelling:

1. Identify incorrect name
2. Locate token
3. Update cardholder name
4. Save changes
5. Verify correction

Update Metadata

Add or update metadata:

1. Locate token
2. Update customer reference
3. Add additional metadata
4. Save changes
5. Confirm update

Deleting Tokens

Delete Process

1. Navigate to Tokens page
2. Find token in list
3. Click Delete button
4. Confirm deletion

warning

• Deletion is permanent
• Cannot be recovered
• Future payments with this token will fail
• Consider deactivating instead if available

When to Delete

Scenario	Action
Customer Request	Delete immediately
Card Expired	Delete if not renewed
Account Closed	Delete all associated tokens
Duplicate Token	Delete duplicate
Data Cleanup	Delete unused tokens

Best Practice: Document reason for deletion in your records.

Processing Token Payments

Using Tokens for Payments

1. Select transaction type (Purchase, Pre-Auth, etc.)
2. Choose Token as payment method
3. Enter or select token value
4. Enter CVV (if required)
5. Enter amount
6. Add reference (optional)
7. Click Process Payment

Benefits

Benefit	Description
Faster Processing	No need to re-enter card details
Reduced Compliance Scope	Less sensitive data handling
Better Experience	Streamlined customer experience
Lower Fraud Risk	Secure token storage
Recurring Payments	Easy subscription management

See Also: Payment User Role

Generating Reports

Step-by-Step Guide

1. Navigate to Tokens

   • Click Tokens tab in left sidebar

2. Set Date Range

   • Click date range selector (top right)
   • Choose preset or custom range

3. Generate Report

   • Click Generate Report button (top right)
   • Report processes
   • CSV file downloads

Date Range Options

Preset Range	Description
Today	Current day tokens
Last 7 days	Past week
Last 30 days	Past month
All Time	Complete token history
Custom Range	Specify exact dates

Report Contents

Token Report Includes:

• Token value (masked)
• Cardholder name
• Card type
• Card category (Credit/Debit)
• Expiry date
• Creation date
• Last used date
• Hierarchy
• Token silo
• Metadata fields
• Status (Active/Expired)

CSV Format:

Token,Cardholder,Card Type,Expiry,Created,Last Used,Status
4111 11AB CDEF 1111,John Smith,Visa,12/26,2026-01-15,2026-01-20,Active

Common Use Cases

Audit & Compliance

Audit and Compliance

1. Generate monthly token report
2. Review active tokens
3. Identify expired tokens
4. Document for compliance

Customer Management

Customer Management

1. Export token list
2. Match to customer database
3. Update customer records
4. Notify of expiring cards

Data Cleanup

Data Cleanup

1. Filter by expiry date
2. Identify expired tokens
3. Contact customers for updates
4. Delete unused tokens