Quick Setup: Getting Started with RGS-CardMasterRGS-CardMaster is a card management and payment-processing solution designed to simplify issuing, tracking, and controlling both physical and virtual cards for businesses and organizations. Whether you’re a small startup issuing employee expense cards or a larger enterprise managing customer gift cards, this guide walks you through a fast and reliable setup so you can start using RGS-CardMaster with minimal friction.
What you’ll accomplish in this guide
By the end of this article you will:
- Understand RGS-CardMaster’s core components and use cases.
- Complete initial account setup and verification.
- Configure card products (virtual and physical).
- Integrate payments and connect funding sources.
- Set up user roles, policies, and spending controls.
- Test workflows and deploy to production.
1 — Before you start: prerequisites
Make sure you have:
- Business information: legal name, address, tax ID.
- A verified bank account or funding source for card funding.
- An admin user email and phone for account verification.
- Developer access (if you plan to integrate via API) and basic knowledge of REST APIs and webhooks.
If you’re planning physical card issuance, allow extra lead time for design approvals and shipping.
2 — Account creation & verification
- Sign up on the RGS-CardMaster dashboard using an admin email.
- Verify your email and complete multi-factor authentication if prompted.
- Provide business details and submit documents requested for KYC (know-your-customer) and AML (anti-money-laundering) checks. Typical documents include business registration, a government ID for the beneficial owner, and proof of address.
- Link and verify a corporate bank account for funding—this often requires micro-deposits or an ACH verification flow.
Verification timing varies by jurisdiction but typically completes within 24–72 hours.
3 — Navigating the dashboard
After verification, you’ll land on the dashboard. Key areas to familiarize yourself with:
- Overview: balance, recent activity, upcoming settlements.
- Cards: create, manage, and freeze/unfreeze cards.
- Card Products: templates for card features (spend limits, MCC restrictions, virtual vs physical).
- Transactions: search, filters, dispute handling.
- Funding & Payouts: link bank accounts, review funding history.
- Developers / API Keys: generate keys and configure webhooks.
- Users & Permissions: invite teammates and assign roles.
4 — Create your first card product
Card products define behavior and capabilities for cards you issue.
Steps:
- Go to Card Products → Create Product.
- Choose card type: Virtual (for immediate use) or Physical (requires printing/shipping).
- Set currency and funding method.
- Configure controls:
- Daily/monthly spend limits (per card or product-level).
- MCC (merchant category code) allow/deny lists.
- Geolocation restrictions (countries or regions).
- Velocity controls (number of transactions per timeframe).
- Enable advanced features as needed:
- Single-use or multi-use virtual numbers.
- Tokenization for wallet provisioning (Apple Pay/Google Pay).
- Split funding or spend categories for accounting.
- Save and activate the product.
Example settings for employee expense cards:
- Type: Virtual
- Currency: USD
- Daily limit: $200
- Allowed MCCs: Travel, Food & Dining, Office Supplies
5 — Issue your first card
With a product configured, issue a card:
Virtual card (instant):
- Cards → Issue Card → Select Product.
- Enter cardholder info (name, email, department).
- Assign spend limits and expiry if different from the product defaults.
- Click Issue. The virtual number appears instantly and can be copied or delivered securely via email/SMS or in-app.
Physical card:
- Select Physical during issuance.
- Provide shipping address and any customization (name embossing, branding).
- Confirm shipping option and production time.
- Submit and track printing/shipping from the dashboard.
6 — Funding cards and managing balances
Cards typically draw from a program balance or linked accounts.
- Pre-fund model: load funds into the program wallet and cards draw down from that pool.
- On-demand authorization: transactions create holds and settlement occurs through the linked funding account.
To add funds:
- Funding & Payouts → Add Funds → Choose bank transfer or card top-up.
- Confirm the amount and expected processing time.
Tip: keep a buffer balance to avoid declined transactions during weekends/holidays.
7 — User roles, permissions & policies
Set roles to control who can create cards, view transactions, or manage funding.
Common roles:
- Admin: full access (account settings, billing).
- Finance Manager: funding, reconciliation, disputes.
- Card Admin: create products and issue cards.
- Auditor/Viewer: read-only access.
Create policies for departmental governance:
- Policy examples: “Marketing cards can only be used for vendor MCCs X, Y, Z” or “Refunds must be approved by Finance Manager.”
8 — Integrations: API & Webhooks
If you’ll automate issuance or reconciliation, use the API.
Typical integration steps:
- Generate API keys in Developers → API Keys.
- Test in sandbox using test keys and simulated transactions.
- Configure webhooks to receive events: card_issued, transaction_authorized, dispute_created, card_frozen.
- Implement secure handling: verify webhook signatures, rotate API keys periodically, and store secrets securely.
Example webhook event payload (JSON):
{ "event": "transaction_authorized", "data": { "transaction_id": "txn_12345", "card_id": "card_67890", "amount": 1250, "currency": "USD", "merchant": "Example Store", "status": "authorized" } } 9 — Testing & staging
Before going live:
- Use sandbox to simulate authorizations, declines, and settlements.
- Test edge cases: declines for insufficient funds, MCC blocks, geo-restrictions, velocity limits.
- Validate reconciliation reports match transactions and settlements.
10 — Monitoring, reporting & disputes
Set up automated alerts and reporting:
- Alerts for low program balance, high decline rates, or suspicious velocity spikes.
- Daily/weekly reconciliation exports in CSV or via API.
- Dispute flow: collect supporting docs, submit via dashboard or API, and track status.
11 — Security best practices
- Enable MFA for all admin accounts.
- Use role-based access control and the principle of least privilege.
- Rotate API keys and store secrets in a secrets manager.
- Monitor logs for unusual patterns and enable IP allowlists for admin access if available.
12 — Common troubleshooting
- Card declined: check program balance, MCC restrictions, geo-controls, and expiry.
- Webhook not received: verify endpoint reachable, check signature verification, and ensure firewall allows requests.
- Funding delay: confirm ACH micro-deposits or bank processing times.
13 — Scaling tips
- Automate card issuance for onboarding flows (e.g., create a virtual card for each new employee).
- Use analytics to identify high spend categories and adjust MCC rules.
- Implement spend policies tied to payroll or project budgets to prevent overspend.
Final checklist (quick)
- [ ] Account verified and funding linked
- [ ] Card product(s) configured
- [ ] First virtual/physical card issued and tested
- [ ] API keys generated and webhooks configured (if needed)
- [ ] Roles and policies set for team members
- [ ] Monitoring, reporting, and dispute processes enabled
If you want, I can: draft example API calls for issuance and webhooks in your preferred language, create a sample policy matrix for roles and permissions, or produce email templates for secure virtual card delivery. Which would you like next?
Leave a Reply