> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/tokenization/es/register-cards-via-batch-file/batch-file-overview.md).

# Descripción general del archivo por lotes

D1 provides a batch processing service that lets the issuer backend execute selected D1 operations in bulk.

The issuer backend prepares a batch input file and uploads it to the D1 platform over an SFTP connection.

When processing is complete, D1 generates a JSON output file that contains the result of each operation in the batch. The issuer backend can then download and process this output file to reconcile and analyze the results.

{% hint style="info" %}
For information about how to create and manage an SFTP account with Thales, contact your Thales delivery team.
{% endhint %}

## Batch file naming convention

Input batch file names must follow one of the following formats:

`"BatchId"-"SeqNumber"-"UNIX_UTC_Timestamp".json`

`"IssuerId"-"BatchId"-"SeqNumber"-"UNIX_UTC_Timestamp".json`

Output batch file names follow the corresponding formats (depending on the input format):

`"BatchId"-"SeqNumber"-"UNIX_UTC_Timestamp"_OUT.json`

`"IssuerId"-"BatchId"-"SeqNumber"-"UNIX_UTC_Timestamp"_OUT.json`

Where:

| Name                 | Description                                                                                      |
| -------------------- | ------------------------------------------------------------------------------------------------ |
| IssuerId             | Optional. The unique identifier of the issuer.                                                   |
| BatchId              | The unique identifier of the batch file.                                                         |
| SeqNumber            | The sequence number of the batch file. Use this when a large batch is split into multiple files. |
| UNIX\_UTC\_Timestamp | A UNIX epoch timestamp in seconds, in UTC.                                                       |

Example:

* BatchId = 87889898
* SeqNumber = 001
* Input file: 87889898-001-1563188489.json
* Output file: 87889898-001-1563188615\_OUT.json

## Supported operations

D1 batch processing supports the following types of operations:

* End user and card registration
* End user and card registration with digital card migration

The following diagram shows a high-level overview of these two operations:

<figure><img src="/spaces/62lLFDcmLCeqqwmy4Fee/files/P54faBUAGsuhpciqlwWX" alt=""><figcaption><p>High-level batch registration and digital card migration flow</p></figcaption></figure>

*Steps 4 and 5 are executed only when digital card migration is requested.*

## Batch campaign configuration

During D1 onboarding, configuration is defined for each registration campaign, including:

* The maximum number of records to process per second
* The maximum duration of the campaign before it expires


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.payments.thalescloud.io/tokenization/es/register-cards-via-batch-file/batch-file-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.