Publisher to Fidel Files (Inbound)

Inbound files contain batch processing files comprised of records that the Publisher sends to Fidel.

For processing, publishers should transmit batch processing files to Fidel on a consistent basis. Those files can be submitted to Fidel in any of the following intervals:

  • Daily (recommended)
  • Weekly
  • Monthly

In order for Fidel to monitor file transfers, publishers should follow the selected schedule. In cases where there is no transaction data, no file needs to be sent.

Publishers should adhere to the following general requirements when sending files to Fidel:

  • File header must be present
  • Required fields in the file must be populated

New and established publishers that want to offer a rewards program to the cardholders, must send batch processing files according to the following:

  • File Format: CSV
  • Property Delimiter: |

The Fidel Inbound Transaction Record and Fidel Inbound CardHolder Record structure can be found on the next section of this document.

Inbound Transaction Record

File Naming Convention (recommended): transaction_oaas_${date}_${publisherName}_v1.csv

FieldDescriptionRequiredExample
Transaction External IdTransaction unique identifierRequired7c1fd29b-6eb2-4c53-8b0b-78d1af03e2d7
Transaction AmountTransaction AmountRequired12.64
Transaction CurrencyTransaction CurrencyRequiredUSD
DatetimeDatetime in UTC when transaction was madeRequired2024-01-01T09:00:00.000Z
CashbackAmount of the reward cashback to the cardholderRequired1.26
Offer IdOffer unique identifierRequired91397a52-f440-41d1-8eef-d2d781bc75cb
Last 4Last 4 digits of the cardRequired3032
Merchant NameMerchant Name where transaction was madeOptionalBrand B
AddressAddress of the merchant locationOptional1849 2nd Ave
CityCity of the merchant locationOptionalNew York
State CodeState Code of the merchant location

Format: ISO 3166-2 code
OptionalNY
Country CodeCountry Code of the merchant location

Format: ISO 3166 Alpha-3
OptionalUSA
MIDMerchant ID where transaction was made, can be used to match transactionsOptional

NOTE:

1. Required for matching offers with linked MIDs
2. It is recommended to use MID Id field instead
3055657
MID IdFidel unique identifier of the MID entityOptional

NOTE:
1.Required for matching offers with linked MIDs
2. Preferable method over usage of MID field
7518f53e-98df-4687-8153-a9ecd70fc352
DescriptorMerchant descriptor that can be used to match transactionsOptionalSTARBUCKS 12345 NEW YORK NY
Publisher NamePublisher name.OptionalPublisher Name
Card External IdCard unique identifierOptional

NOTE: Required for Incrementality Reporting
07a8d178-2d88-4421-a502-0534ff477474
SchemeScheme of the transactionOptionalMastercard
TypeTransaction TypeOptionalClearing
AuthCodeTransaction Auth CodeOptionalA1B2C3
Issuing BINIssuing Bank Identification NumberOptional411111
ARNAcquiring Reference Number, Unique identifier assigned to a transaction by the acquirer or payment processorOptional74659483729384716283920
Custom {1...N}Custom fields as free text for passthroughOptional'Custom 1': 'value1',
'Custom 2': 1234,
'Custom 3': true
Activation DateActivation Date to be used on offers with activation enabledOptional2025-05-28T12:53:45

Inbound CardHolder Record

File Naming Convention (recommended): cardholder_oaas_${date}_${publisherName}_v1.csv

FieldDescriptionRequiredExample
Offer IdOffer unique identifierRequired91397a52-f440-41d1-8eef-d2d781bc75cb
Card External IdCard unique identifierRequired07a8d178-2d88-4421-a502-0534ff477474
Incrementality GroupIncrementality Group
Possible values:

- holdout
- treatment
Requiredholdout

Inbound Aggregated CardHolder Record

File Naming Convention (recommended): aggregated_cardholder_oaas_${date}\_${publisherName}_v1.csv


FieldDescriptionRequiredExample
Offer IdOffer unique identifierRequired91397a52-f440-41d1-8eef-d2d781bc75cb
Incrementality GroupIncrementality Group
Possible values:

- holdout
- treatment
Requiredholdout
Eligible UsersNumber of users that are part of the incrementality groupRequired1000000
Total TransactionsNumber of total transactions made by the users of this incrementality groupRequired10000000
Total Transactions AmountTotal transactions spend amount by users of this incrementality groupRequired50000000
Transacted UsersNumber of unique users that are part of this incrementality group and have transacted at least onceOptional

NOTE: Without this, Fidel is not able to calculate the incremental number of users that a given Offer brought to the brand
500000