Once you've submitted a bulk import, everything about it lives in the imports table under Imports & exports — its progress, its per-row results, and a downloadable report.

To run an import, see Creating multiple Virtual Cards with a CSV file.

Go to Imports & exports. Every import you've run is listed in the table, most recent first.

You don't need to stay on the page while an import runs. Once you've submitted it, the job keeps going whether or not your browser is open — come back to the imports table whenever you like.

To find an older import, use the status dropdown or Filter by to narrow the table by action type or by the person who submitted it.

Each import gets a status based on how its rows turned out.

Partial is normal, not an error. Once an import passes validation and starts running, each row is created on its own, so a mix of outcomes is expected on larger files.

Open an import to see every row and how it turned out.

Skipped is good news. It means Fluz found a card with that nickname already on your account and didn't make a duplicate. It doesn't mean anything is wrong with your file.

Read the reason before you re-import a failed row. Some failures happen after the card was created — for example when the card was issued but its details couldn't be displayed. Re-importing those rows creates a second card. See Why did my Virtual Card CSV import fail? for what each message means.

Yes, but not with a button. Build a new CSV containing only those rows and run a fresh import. Your report tells you exactly which rows to include.

If the rows that succeeded had nicknames, you can safely re-import the whole file instead — the successful rows come back as Skipped rather than creating duplicates.

Two things can go wrong after a card exists. Both have a fix on the import's page, and neither needs a re-import:

In both cases the card exists and is usable. Don't re-import the row.

When an import finishes, a Download link appears in its report column. The report is a CSV listing every row with its outcome, the details of each card created, and the specific reason for anything that didn't go through.

You can also select several imports using the checkboxes and download their reports together.

Treat this file as sensitive. It contains card details for every card in the batch. Store it securely, share it only with people who need it, and delete it when you're done.

You can cancel one that's still running, from the imports list. Rows that had already been created stay created — cancelling stops the remaining ones.

If you see Job is not in a cancellable state, the import had already finished, failed, or been cancelled. Reload the page.

No. Once you enter your PIN and confirm, the rows are issued as real cards, and cards can't be deleted. Review carefully at the confirmation step.

If you created cards you don't want, you can freeze them so they can't be used — see Freezing/unfreezing your Virtual Card.

No. Bulk import creates cards that belong to your account. If you fill in the email_address and role_level columns, that teammate is granted access to the card inside your organization — it doesn't deliver a card to someone outside it.

Only one Virtual Card import can run per account at a time, including one started by a different person on your team. A Virtual Card import and a different type of import can run at the same time.

You can still upload and preview a new file while an import is running — you just can't submit it until the first one finishes.

Related articles