Resumen de archivos por lotes
Batch file naming convention
Name
Description
Supported operations
Batch campaign configuration
Última actualización
¿Te fue útil?
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.
For information about how to create and manage an SFTP account with Thales, contact your Thales delivery team.
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:
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
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:
Steps 4 and 5 are executed only when digital card migration is requested.
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
Última actualización
¿Te fue útil?
¿Te fue útil?