Skip to main content
Use Cards to identify card records, review activity already recorded in Conto, and keep reconciliation context in one place. Conto stores masked details such as the card name, brand, and last four digits; it does not need the full card number.

​
Add a manual record

Open Cards and choose Add card. Enter a name, the last four digits, brand, and card type. A manual record does not connect Conto to the card processor, distribute card credentials, or change processor settings. The processor remains the authoritative source for balances, posted charges, disputes, and the card’s usable state.

​
Understand card sources

  • Manual record means the card was added using masked details for identification and reconciliation.
  • A named provider source means an existing card record is bound to that provider. When a refresh action is available, it updates the local record from the provider.

​
Conto Card Access (maintenance reference)

Conto Card Access is a maintenance-only private fallback for existing pilots that use a customer-owned card. It is not a new integration surface: new connected-card work should use the shared Cards product surface instead. Existing pilots can use the direct recovery workspace to review retained policy assignments and reconciliation work. Card Access controls only the integrated agent path and does not control the issuer or card network, so canBypass=true.

​
Card status actions

For a manual record, pause, resume, and archive actions update the record in Conto only. They do not pause, resume, or cancel the underlying card at its processor. For a provider-bound card, Conto offers a provider action only when the corresponding connection is available. The action result describes the state recorded in Conto; verify sensitive lifecycle changes with the card processor.

​
Linked context

Existing agent and policy links are shown as reconciliation context. They do not by themselves give an agent card credentials or prove that the processor enforces a Conto policy. Manage actual cardholder access and processor-side controls with the card provider.

​
Reconcile activity

The card detail page shows activity available in Conto, including:
  • a stable Conto transaction ID;
  • merchant, amount, currency, and date;
  • a normalized status such as authorized, completed, declined, or refunded.
Tracked totals include only activity recorded in Conto and may differ from the processor ledger. Reconcile against the processor statement and use the Conto transaction ID as the local reconciliation key.

​
Session API

Dashboard sessions can use: All routes are scoped to the selected organization and require the corresponding card or policy permission.