Prepare and manage corporate cards
Availability unconfirmed: check eligibility first
Public merchant access to corporate cards, fund pools, cardholders, issuance, spending approvals and card transactions remains unconfirmed. This page is a preparation checklist and conditional guide for enabled accounts, not permission for a payment account to issue cards. Confirm card types, regions, verification, fees and spending scope with your verified onboarding contact. No particular network, issuer, worldwide acceptance, issuance time or shipping schedule is promised.
Corporate cards support business spending, separately from customer Checkout payments and IPP settlements. Card-purchase refunds are also separate from refunds of merchant receipts; do not use the payment refund flow to resolve a card purchase.
Prepare access and review the fund pool
- Prepare business and representative information and confirm the region, eligible cardholders and actual KYB or other verification requirements. Verification approval still requires separate card access confirmation.
- Define administrator, cardholder, approver and finance duties. Confirm who may issue cards, view sensitive information, change limits and fund the pool.
- If a pool is offered, distinguish available, reserved and spent amounts. Authorization holds are not final spending, and the entire balance is not necessarily available again.
- If funding is offered, use its current supported source, currency, network and actual payment instructions. Check the destination, fees and funding order first. After sending, track the original record instead of transferring again because a page has not refreshed.
- If automatic funding is offered, confirm triggers, funding source and failure notifications and assess its authorization. Completed IPP settlement does not establish automatic funding of the card pool.
Add cardholders and issue cards
Use these steps only for operations actually enabled:
- Search existing cardholders and verify name, contact and department. Eligibility for team-member selection or manual entry comes from the current screen. A cardholder does not automatically have dashboard administration rights.
- Confirm the offered card type and intended use. For a physical card, verify the shipping address and service region rather than promising delivery because an address was accepted.
- Set offered transaction, daily or monthly limits, spending categories and applicable rules. Check consistency rather than relying on an unreviewed template.
- Review the recipient, type and limits before submission and retain the application identifier. For batch issuance, inspect each person's result; retrying the whole batch could issue another card to a successful recipient.
- Inspect the actual issuance and activation result before planning spending. Submission, a success message or an email does not replace the current card state.
View card numbers or CVV only when authorized, offered and verified through the required secondary check. Keep them out of tickets, group chats and ordinary reconciliation sheets. Wallet private keys and login recovery codes are not materials to send for issuance.
Control spending and approvals
If rule management is enabled, inspect the individual, department, template or global settings actually effective for the card before changing limits or category and merchant restrictions. Check affected cards before saving and reload afterward; do not assume one configuration layer overrides every restriction.
If an approval queue is offered, verify the card, cardholder, merchant, amount and trigger before approving or rejecting with the proper permission and a recorded reason. Approval does not establish final settlement. Verify actual timeout rules and outcomes without assuming automatic approval, a fixed delay or guaranteed notifications.
For a lost card or suspicious purchase, freeze the affected card when supported and authorized, verify the result and contact verified support. Freezing does not reverse an already-authorized or settled transaction. Before cancellation, inspect pending transactions, refunds and recurring charges and assign follow-up responsibility.
Reconcile transactions and receipts
- Filter real transactions by period, timezone, cardholder, card and state. Record original and settlement currencies, merchant and transaction identifier.
- Separate pending authorization or reserved funds, final settlement, declines and refunds. Pending amounts may change; do not replace final facts with estimates.
- If attachments are supported, attach receipts to the correct transaction and check merchant and amount. Follow current file requirements and omit full card numbers and CVV.
- If statements and exports are offered, check coverage, fees, exchange rates, refunds and fund-pool movement against business accounts. Preserve export conditions using reports.
Handle exceptions and offboarding
| Situation | Next action |
|---|---|
| Issuance unavailable or application rejected | Check card access, verification, region and permissions; a higher platform plan does not necessarily resolve it |
| Purchase declined | Inspect card state, available funds, limits, category or merchant restrictions and approval result; avoid repeated charges or blind funding |
| Hold remains reserved | Query the original transaction and give its identifier and latest state to support; do not promise release after a fixed period |
| Unknown funding or transaction result | Inspect original applications and funds records rather than resubmitting because a balance is stale |
| Refund missing from card accounts | Inspect the original purchase and refund and follow its supported service channel, without substituting a merchant Checkout refund status |
| Member leaves | Inventory and freeze or cancel their cards with proper access and handle receipts, pending transactions and refunds; removing team access does not establish disabled cards |
Verify actual card states, approvers and recurring-charge arrangements before completing team offboarding.