About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.
When to run it
When to run it
When credit card authorization data (auth blobs) takes up too much database space, for transactions that are older than your linked-refund period.
How often
As a recurring batch job once the backlog is archived; later runs take less time.
Batch settings
A recurring batch job. Start with a large Minimum transaction age in days and lower it step by step, so each run handles fewer transactions.
What the output shows
Payment tokens and signature capture data (PaymentAuthorization, PaymentCaptureToken, PaymentCardToken and SigCapData) of older card transactions are exported to a ZIP file in Azure Blob storage and removed from the database, or just deleted. Returns of those transactions then need standalone refunds.
Go to Retail and Commerce > Retail and Commerce IT > Clean up > Archive credit card transaction data.
In Minimum transaction age in days, enter the period in which customers can still get linked refunds to the original card, for example 730 for two years. Corresponding transaction date then shows the date before which records are affected.
Set Delete data without archiving to Yes only if the payment tokens and signature data should be deleted instead of exported to Azure Blob storage. Archiving needs document management to be set up.
Leave Use compression off on version 10.0.49 and later; compression now has its own Compress credit card transaction data job.
Set the recurrence and batch group in Run in the background; batch processing is always on for this job.
Select OK and confirm the archive prompt with Yes, then check that the job finishes. The first run on a large backlog can take hours or days.
No: Archived data can't easily be restored and deleted data is gone. Set the minimum age so that no transaction still needs a linked refund. Microsoft Learn
If you change it later
Archived data can't easily be restored, so returns of affected transactions must use standalone refunds instead of linked refunds. Microsoft Learn
Technical architect
5Technical
Menu item
RetailTransactionPaymentTransArchiveChecked in Dynamics 365
Form
DialogChecked in Dynamics 365
Roles to set it up and use it
To use itRetail operations manager RetailOperationsManagerGive people one of these roles. On this system, 1 role can run this page.Checked in Dynamics 365