Skip to main content
Version: 2.0

Batch Transfer

Batch transfers are applicable for doing a historical backfill or batch integration:

  1. Historical Backfill: Upload historical transaction data to enrich Fraudio's context and improve model training and historical data analysis, leading to better-tuned fraud detection for your specific needs.

  2. Batch Integration: While real-time API integration is always the preferred method and highly recommended, doing a batch integration provides an alternative way to send transaction data in bulk on a scheduled basis when API integration is not feasible. Please note that batch integration is not recommended as it may not provide the same level of accuracy and timeliness as real-time API integration.


Historical Backfill​

Requirements​

  • Adherence to API Data Schemas: Ensure that the historical data adheres to the data schemas of the API Endpoints that are used. For a detailed description of the batch data schemas, please refer to the Batch Data Schemas section.

  • Consistency with Data Quality of Live Data: Ensure that the quality of historical data is consistent with the transactions sent to the API. It is important to avoid differences in data distributions between historical and live data to ensure consistency and accuracy in our fraud detection models. This includes maintaining uniformity in data fields, data formats, field values, and metadata to prevent discrepancies that could affect fraud detection accuracy.

  • Consistency of Data Volume: Ensure that there are no gaps in the data by verifying that transactions are present for each day to maintain completeness. It is recommended to send at least 24 months of historical data.

  • RFC-4180 CSV Format: Batch data must be provided in CSV format, conforming to the RFC-4180 specification. This ensures reliable parsing of all fields and prevents common data formatting issues.

  • Minimized Gap Between Historical Data and Live Data: To maintain the highest level of accuracy, it is recommended to minimize the time gap between sending historical data and starting to send live transactions to the Financial Events Screening endpoint. This ensures continuity and accuracy in our fraud scoring models, providing effective fraud protection.

tip

Before sending the entire historical dataset, it is advisable to first send a sample of the data. This allows for quick validation and reduces the risk of unnecessary delay.

Batch Data Schemas​

The batch data that is sent should follow the same data schemas as the data that is sent to the API. For every event type that is sent to the API, we would like to receive the corresponding historical data in batch. Therefore it is important to align with the data that is sent to the API.

For historical batches, we recommend following the schema of the Financial Events Enrichment endpoint. It is not necessary to split events by transactions that require scoring versus enrichment. Include post-auth information for complete context (for example authorization response fields on 0110 events).

If you prefer, you may also send transaction events separately as on the live API. That typically involves more effort and is generally not necessary for batch processing. In that case, follow Financial Events Screening and Financial Events Enrichment (including authorization response events for post-auth fields).

Event types you may include in the same Enrichment-shaped batch:

  • Financial events (purchases, captures, refunds, and similar) via Financial Events Enrichment
  • Dispute events (dispute, for example chargebacks and TC40/SAFE) via dispute
  • Bank transfers (bank_transfer) via bank_transfer
  • Entity updates (merchants, cards, wallets, and other entity types) via entities-only with an empty events array
Toggle to view the Financial Events Enrichment schema used for batch
FieldData TypePayment Fraud (Issuer)Payment Fraud (Acquirer / Processor)Merchant Fraud / AMLDescription
events[].<event_type>ObjectRequiredRequiredRequired
Exactly one event-type payload key on each event (oneOf), e.g. card_network_transaction, wallet_payment, wallet_transfer, bank_transfer, dispute. The key names the event kind; its object holds type-specific fields.
events[].idStringRequiredRequiredRequired
Unique identifier of the event.
events[].timestampDoubleRequiredRequiredRequired
UTC Unix timestamp (seconds; may be fractional) of the event.
events[].lifecycle_idStringOptionalOptionalOptional
Client lifecycle identifier shared across chained events in the same payment lifecycle. When omitted, it defaults to the event id. Repeat the same value on every related message, including follow-up card-network messages, transfer status updates, and dispute events that refer back to the payment. For the card-network Retrieval Reference Number (ISO 8583 DE037), use card_network_transaction.rrn.
events[].labelsObject[String, String]OptionalOptionalOptional
Optional flat map of client-defined string keys to string values. Keys have no Fraudio-defined schema. Nested objects, arrays, and non-string values are not allowed.
events[].card_network_transaction.mtiStringOptionalOptionalOptional
ISO 8583 MTI when applicable.
events[].card_network_transaction.rrnStringOptionalOptionalOptional
Retrieval Reference Number (ISO 8583 DE037) for this card-network message when available. Distinct from event-level lifecycle_id, which links related events across a payment lifecycle.
events[].card_network_transaction.transaction_typeStringOptionalOptionalOptional
ISO 8583 DE003 transaction type when applicable.
events[].card_network_transaction.currencyStringOptionalOptionalOptional
ISO 4217 alphabetic currency code (3 letters, e.g. EUR).
events[].card_network_transaction.currency_unitStringOptionalOptionalOptional
major or minor.
events[].card_network_transaction.amountDoubleOptionalOptionalOptional
Amount in the currency and unit provided.
events[].card_network_transaction.amount_in_base_currencyDoubleOptionalOptionalOptional
Amount converted to the client's base currency (same unit as currency_unit when that field applies). Optional when the event currency already is the base currency, or when FX conversion is unavailable.
events[].card_network_transaction.successStringOptionalOptionalOptional
Overall result of the transaction. Accepted values: true (fully completed without technical or non-technical failures); false (any part failed or did not meet criteria); none (outcome uncertain or not yet known). Use true only for fully successful transactions.
events[].card_network_transaction.response_codeStringOptionalOptionalOptional
Authorization or financial response code from the issuer/network (for example ISO 8583 DE039). Typical on 0110 / post-auth events.
events[].card_network_transaction.eciStringOptionalOptionalOptional
Electronic Commerce Indicator from 3-D Secure or equivalent authentication.
events[].card_network_transaction.avs_resultStringOptionalOptionalOptional
Address Verification System (AVS) result code.
events[].card_network_transaction.cvv_resultStringOptionalOptionalOptional
Card verification value (CVV/CVC) check result.
events[].card_network_transaction.cavv_resultStringOptionalOptionalOptional
Cardholder Authentication Verification Value (CAVV) or equivalent authentication result.
events[].wallet_transfer.sister_transaction_idStringOptionalOptionalOptional
ID of the counterpart record for the same transfer, used when a single transfer is represented by two records (e.g. one per side). Same semantics as Screening.
events[].wallet_transfer.statusStringOptionalOptionalOptional
Transfer status.
- pending: the transfer request is created.
- accepted: the transfer is authorised and the funds are reserved.
- completed: the transfer settled and the funds are deducted.
- rejected: the transfer is refused, before acceptance or by the counterparty. Put the cause in status_reason.
- returned: after settlement, the counterparty sends the funds back.
On a status-only enrichment, send the later status here.
events[].wallet_transfer.status_reasonStringOptionalOptionalOptional
Normalized reason for the status when applicable (e.g. insufficient_funds).
events[].wallet_transfer.status_reason_codeStringOptionalOptionalOptional
Scheme or client reason code when applicable.
events[].wallet_transfer.payment_referenceStringOptionalOptionalOptional
Free-text payment reason / narrative. Omit on a status-only enrichment when already sent on the scored event.
events[].wallet_transfer.sender.refs.authorStringOptionalOptionalOptional
Reference to an author entity when someone other than a wallet holder created the payment. Same shape as Screening.
events[].bank_transfer.currencyStringOptionalOptionalOptional
ISO 4217 alphabetic currency code (3 letters, e.g. EUR) for a bank_transfer. Omit on a status-only enrichment when already sent on the scored event.
events[].bank_transfer.currency_unitStringOptionalOptionalOptional
major or minor. Omit on a status-only enrichment when already sent on the scored event.
events[].bank_transfer.amountDoubleOptionalOptionalOptional
Transfer amount. Omit on a status-only enrichment when already sent on the scored event.
events[].bank_transfer.amount_in_base_currencyDoubleOptionalOptionalOptional
Amount converted to the client's base currency (same unit as currency_unit when that field applies). Optional when the event currency already is the base currency, or when FX conversion is unavailable. Omit on a status-only enrichment when already sent on the scored event.
events[].bank_transfer.railStringOptionalOptionalOptional
Clearing path for the transfer, e.g. sepa, sepa_inst, faster_payments, swift. Extensible string. Omit on a status-only enrichment when already sent on the scored event.
events[].bank_transfer.tenant_roleStringOptionalOptionalOptional
Role of your tenant in the transfer. sender when your tenant is the sender, receiver when your tenant is the receiving side, on_us when both the sender and the receiver belong to your tenant. Omit on a status-only enrichment when already sent on the scored event.
events[].bank_transfer.statusStringOptionalOptionalOptional
Transfer status.
- pending: the transfer request is created.
- accepted: the transfer is authorised and the funds are reserved.
- completed: the transfer settled and the funds are deducted.
- rejected: the transfer is refused, before acceptance or by the counterparty. Put the cause in status_reason.
- returned: after settlement, the counterparty sends the funds back.
Typical enrichment-only field when the initiation was scored earlier.
events[].bank_transfer.status_reasonStringOptionalOptionalOptional
Normalized reason for a non-success status, e.g. account_closed. Typical enrichment-only field.
events[].bank_transfer.status_reason_codeStringOptionalOptionalOptional
Scheme or client reason code when applicable (e.g. ISO 20022 AC04). Typical enrichment-only field.
events[].bank_transfer.payment_referenceStringOptionalOptionalOptional
Free-text payment reason / narrative supplied by the payer. Omit on a status-only enrichment when already sent on the scored event.
events[].bank_transfer.sender.refs.authorStringOptionalOptionalOptional
Reference to an author entity on the debit / sender side when someone other than an account holder created the payment. Omit when the holder created the payment, or on a status-only enrichment.
events[].wallet_payment.currencyStringOptionalOptionalOptional
ISO 4217 alphabetic currency code (3 letters, e.g. EUR).
events[].wallet_payment.currency_unitStringOptionalOptionalOptional
major or minor.
events[].wallet_payment.amountDoubleOptionalOptionalOptional
Amount in the currency and unit provided.
events[].wallet_payment.amount_in_base_currencyDoubleOptionalOptionalOptional
Amount converted to the client's base currency (same unit as currency_unit when that field applies). Optional when the event currency already is the base currency, or when FX conversion is unavailable.
events[].wallet_payment.mccStringOptionalOptionalOptional
Merchant category code as processed on this wallet payment. Distinct from registered MCCs on a merchant_account or sub_merchant entity. Do not use card_network_transaction for wallet-to-merchant payments.
events[].wallet_payment.statusStringOptionalOptionalOptional
Payment status.
- pending: the payment request is created.
- accepted: the payment is authorised and the funds are reserved.
- completed: the payment settled and the funds are deducted.
- rejected: the payment is refused, before acceptance or by the counterparty. Put the cause in status_reason.
- returned: after settlement, the counterparty sends the funds back.
On a status-only enrichment, send the later status here.
events[].wallet_payment.status_reasonStringOptionalOptionalOptional
Normalized reason for the status when applicable (e.g. insufficient_funds).
events[].wallet_payment.status_reason_codeStringOptionalOptionalOptional
Scheme or client reason code when applicable.
events[].wallet_payment.payment_referenceStringOptionalOptionalOptional
Free-text payment reason / narrative. Omit on a status-only enrichment when already sent on the scored event.
events[].wallet_payment.sender.refs.authorStringOptionalOptionalOptional
Reference to an author entity when someone other than a wallet holder created the payment. Same shape as Screening.
events[].card_network_transaction.pos_entry_modeStringOptionalOptionalOptional
ISO POS entry mode when applicable. When channel is omitted, Fraudio derives it from this field and pos_condition_code: pos_condition_code 08/09 map to moto; pos_entry_mode 010/10/011/11/012/12 map to ecom; other entry modes map to pos; missing or 00 entry mode is treated as ecom.
events[].card_network_transaction.pos_condition_codeStringOptionalOptionalOptional
ISO POS condition code when applicable. Codes 08/09 map to channel moto (see pos_entry_mode for the full channel derivation).
events[].card_network_transaction.channelStringOptionalOptionalOptional
Channel of the card payment. Accepted values: ecom (ecommerce), pos (in person), moto (mail or telephone order), atm (ATM).
events[].card_network_transaction.channel_subtypeStringOptionalOptionalOptional
Channel subtype when known. Accepted values: paymentlink (PayByLink), telephoneorder, mailorder.
events[].card_network_transaction.recurringStringOptionalOptionalOptional
Whether the payment is recurring. Accepted values: true, false, none (unknown).
events[].card_network_transaction.recurring_lifecycle_idStringOptionalOptionalOptional
lifecycle_id of the first payment in the recurring series. Repeat it on every cycle. When it equals this event's lifecycle_id, this is the initial recurring transaction.
events[].card_network_transaction.dynamic_descriptorStringOptionalOptionalOptional
Dynamic descriptor returned by the processor; text that appears on the cardholder bank statement.
events[].card_network_transaction.merchant_advice_codeStringOptionalOptionalOptional
Merchant advice code from the payment processor: reason for a decline and how the merchant may retry.
events[].card_network_transaction.mccStringOptionalOptionalOptional
Merchant category code as processed on this event/transaction. Distinct from registered MCCs on a merchant_account or sub_merchant entity.
events[].<event_type>.sender.refs.cardStringOptionalOptionalOptional
Reference to a card entity when applicable.
events[].<event_type>.sender.refs.walletStringOptionalOptionalOptional
Reference to a wallet entity when the wallet is the sender (e.g. wallet payment, wallet withdrawal, payout events).
events[].<event_type>.sender.refs.merchant_businessStringOptionalOptionalOptional
Reference to a merchant_business entity when the merchant is the initiating party (e.g., wallet withdrawal, payout, chargeback lifecycle). Should be included alongside wallet reference for wallet-based events.
events[].<event_type>.sender.refs.bank_accountStringn.a.n.a.Optional
Reference to a bank_account entity when the bank account is the sender (e.g. wallet deposit, or a wallet_payment funded from a linked bank account).
events[].<event_type>.sender.ipStringOptionalOptionalOptional
Sender IP address when applicable.
events[].<event_type>.sender.user_agentStringOptionalOptionalOptional
HTTP User-Agent string of the sender when the interaction is browser- or app-based.
events[].<event_type>.sender.street_addressStringOptionalOptionalOptional
Street address associated with the sender location when known.
events[].<event_type>.sender.cityStringOptionalOptionalOptional
City associated with the sender location when known.
events[].<event_type>.sender.state_codeStringOptionalOptionalOptional
State, province, or region code associated with the sender location when known.
events[].<event_type>.sender.postal_codeStringOptionalOptionalOptional
Postal / ZIP code associated with the sender location when known.
events[].<event_type>.sender.country_codeStringOptionalOptionalOptional
Country of the sender on the transaction payload (ISO 3166-1 alpha-3, e.g. NLD). Applies to every event type that has a sender, including card_network_transaction, bank_transfer, wallet_transfer, and wallet_payment.
events[].<event_type>.receiver.refs.walletStringOptionalOptionalOptional
Reference to a wallet entity when the wallet is the receiver (e.g., wallet deposit events).
events[].<event_type>.receiver.refs.merchant_businessStringOptionalOptionalOptional
Reference to a merchant_business entity when the merchant is the receiving party. Should be included alongside wallet reference for wallet deposit events.
events[].<event_type>.receiver.refs.bank_accountStringn.a.n.a.Optional
Reference to a bank_account entity when the bank account is the receiver (e.g., wallet withdrawal events).
events[].<event_type>.receiver.refs.acceptorStringOptionalOptionalOptional
Reference to an acceptor entity when applicable.
events[].<event_type>.refs.gatewayStringOptionalOptionalOptional
Reference to the payment gateway (intermediary).
events[].<event_type>.refs.acquirerStringOptionalOptionalOptional
Reference to the acquirer (intermediary).
events[].<event_type>.refs.processorStringOptionalOptionalOptional
Reference to a processor entity (payment processor / PSP intermediary appointed to handle transactions for merchant acquiring). Distinct from acquirer and gateway.
events[].<event_type>.receiver.ipStringOptionalOptionalOptional
Receiver IP address when applicable.
events[].<event_type>.receiver.user_agentStringOptionalOptionalOptional
HTTP User-Agent string of the receiver when the interaction is browser- or app-based.
events[].<event_type>.receiver.street_addressStringOptionalOptionalOptional
Street address associated with the receiver location when known.
events[].<event_type>.receiver.cityStringOptionalOptionalOptional
City associated with the receiver location when known.
events[].<event_type>.receiver.state_codeStringOptionalOptionalOptional
State, province, or region code associated with the receiver location when known.
events[].<event_type>.receiver.postal_codeStringOptionalOptionalOptional
Postal / ZIP code associated with the receiver location when known.
events[].<event_type>.receiver.country_codeStringOptionalOptionalOptional
Country of the receiver on the transaction payload (ISO 3166-1 alpha-3, e.g. NLD). Applies to every event type that has a receiver, including card_network_transaction, bank_transfer, wallet_transfer, and wallet_payment.
events[].<event_type>.receiver.geocoordinatesStringOptionalOptionalOptional
Receiver geocoordinates.
entities[]ArrayOptionalOptionalOptional
Top-level array of entity objects. Entities are correlated to events through refs, not by nesting.
entities[].<entity_type>ObjectOptionalOptionalOptional
Exactly one entity-type payload key on the array item (oneOf), e.g. card_account, card, shopper, shopper_device, bin, merchant_account, sub_merchant, processor. The key names the entity kind; its object holds entity fields (id, timestamp, …).
entities[].<entity_type>.idStringOptionalOptionalOptional
Stable entity identifier.
entities[].<entity_type>.timestampDoubleRequiredRequiredRequired
UTC Unix timestamp (seconds; may be fractional) at which this entity snapshot was observed / is valid.
entities[].<entity_type>.labelsObject[String, String]OptionalOptionalOptional
Optional flat map of client-defined string keys to string values. Keys have no Fraudio-defined schema. Nested objects, arrays, and non-string values are not allowed.
entities[].<entity_type>.nameStringOptionalOptionalOptional
Entity name when available.
entities[].<entity_type>.country_codeStringOptionalOptionalOptional
Country code when available (ISO 3166-1 alpha-3, e.g. NLD). Applies to location-bearing entities including issuer, acquirer, gateway, processor, acceptor, merchant_business, merchant_account, sub_merchant, and institution.
entities[].<entity_type>.limitprofileStringOptionalOptionalOptional
Merchant limit profile (can be partial update; null to clear).
entities[].<entity_type>.mccsArrayOptionalOptionalOptional
Registered / assigned MCC list on a merchant_account or sub_merchant entity. On a sponsored seller this is entities[].sub_merchant.mccs. Do not send on merchant_business; use event.card_network_transaction.mcc or event.wallet_payment.mcc for the as-processed code on a payment.
entities[].sub_merchantObjectOptionalOptionalOptional
Sponsored seller that accepts payments under a Payment Facilitator. Uses the standard entity id and timestamp. Reference it from the event with receiver.refs.sub_merchant.
entities[].sub_merchant.nameStringOptionalOptionalOptional
Name of the sponsored seller.
entities[].sub_merchant.country_codeStringOptionalOptionalOptional
Country of the sponsored seller (ISO 3166-1 alpha-3, e.g. NLD).
entities[].sub_merchant.mccsArrayOptionalOptionalOptional
Registered / assigned MCC list for this sponsored seller. The MCC used on a specific payment stays on the event.
entities[].sub_merchant.refs.payfacStringOptionalOptionalOptional
Id of the Payment Facilitator (payfac) this seller processes under.
entities[].sub_merchant.refs.merchant_businessStringOptionalOptionalOptional
Id of the merchant_business for this sponsored seller, when you send one.
entities[].merchant_account.midStringOptionalOptionalOptional
Processor- or acquirer-assigned Merchant ID on a merchant_account entity.
entities[].acceptor.terminal_typeStringOptionalOptionalOptional
Cardholder-Activated Terminal (CAT) type on an acceptor entity (e.g. cat1, cat2, cat6, cat9).
entities[].acceptor.country_codeStringOptionalOptionalOptional
Country where the acceptor (terminal / ATM) is located (ISO 3166-1 alpha-3).
entities[].acceptor.street_addressStringOptionalOptionalOptional
Street address of the acceptor (terminal / ATM) when known.
entities[].acceptor.cityStringOptionalOptionalOptional
City where the acceptor (terminal / ATM) is located when known.
entities[].acceptor.state_codeStringOptionalOptionalOptional
State, province, or region code of the acceptor location when known.
entities[].acceptor.postal_codeStringOptionalOptionalOptional
Postal / ZIP code of the acceptor location when known.
entities[].card.activated_atDoubleOptionalOptionalOptional
UTC Unix timestamp (seconds; may be fractional) when this card instance was activated.
entities[].binObjectOptionalOptionalOptional
BIN (IIN) entity payload under the bin key. id is the BIN/IIN value. Link from card / card_account via refs.bin.
entities[].bin.brandStringOptionalOptionalOptional
Card scheme / brand for this BIN range (e.g. visa, mastercard).
entities[].bin.country_codeStringOptionalOptionalOptional
Country associated with the BIN range (ISO 3166-1 alpha-3).
entities[].bin.card_typeStringOptionalOptionalOptional
Card type for this BIN range (e.g. credit, debit).
entities[].shopper_deviceObjectOptionalOptionalOptional
Shopper device entity payload under the shopper_device key. Correlate only via entities[].shopper.refs.shopper_device.
entities[].shopper_device.osStringOptionalOptionalOptional
Operating system of the shopper device (e.g. ios, android, windows). Any OS string is accepted.
entities[].processorObjectOptionalOptionalOptional
Payment processor entity payload under the processor key. Correlate via events[]..refs.processor.
entities[].processor.nameStringOptionalOptionalOptional
Display name of the payment processor.
entities[].processor.country_codeStringOptionalOptionalOptional
Country of the payment processor (ISO 3166-1 alpha-3) when known.
entities[].gatewayObjectOptionalOptionalOptional
Payment gateway entity payload under the gateway key. Correlate via events[]..refs.gateway.
entities[].gateway.nameStringOptionalOptionalOptional
Display name of the payment gateway.
entities[].gateway.country_codeStringOptionalOptionalOptional
Country of the payment gateway (ISO 3166-1 alpha-3) when known.
entities[].acquirer.country_codeStringOptionalOptionalOptional
Country of the acquiring institution (ISO 3166-1 alpha-3) when known.
entities[].bank_accountStringn.a.n.a.Optional
Bank account entity payload under the bank_account key (IBAN or equivalent national account number fields).
entities[].bank_account.ibanStringn.a.n.a.Optional
Legacy IBAN field for bank_account entities. Prefer account_number with account_number_scheme: "iban" (see Screening bank_account).
entities[].<entity_type>.refs.merchant_businessStringn.a.n.a.Optional
Reference from another entity to a merchant_business (e.g. wallet or bank account belonging to the merchant).
entities[].<entity_type>.refs.binStringOptionalOptionalOptional
On card or card_account: id of the linked bin entity (Bank Identification Number / IIN range). Do not put BIN on acquirer or issuer; use the bin entity instead.
entities[].shopper.refs.shopper_deviceStringOptionalOptionalOptional
On a shopper entity: id of the linked shopper_device when known.
entities[].merchant_business.refs.ubosArrayOptionalOptionalOptional
Ids of linked ubo entities for this merchant business (one or many). Same shape as Screening.
entities[].merchant_business.urlStringOptionalOptionalOptional
Primary website URL of the merchant business when known.
entities[].wallet.statusStringOptionalOptionalOptional
Wallet relationship status when known (e.g. active). Same shape as Screening.
entities[].wallet.refs.accountholdersArray[String]OptionalOptionalOptional
Ids of accountholder entities who hold this wallet. Same shape as Screening.
entities[].wallet.refs.institutionStringOptionalOptionalOptional
Id of the institution (EMI / wallet operator) that books this wallet. Same shape as Screening.
entities[].wallet.refs.merchant_businessStringOptionalOptionalOptional
Id of the linked merchant_business for a merchant or corporate wallet. Same shape as Screening.

How to transfer historical data to Fraudio​

Transfer historical data to Fraudio by uploading CSV files to our Amazon S3 storage. For alternative data transfer methods, contact Fraudio.

  1. Get Fraudio credentials. Request credentials to authenticate with the AWS CLI from Fraudio, including your CUSTOMER_NAME, which is needed to view and upload files.
  2. Install the AWS CLI. Follow the official guide.
  3. Log in to AWS. Run aws configure and enter your key ID and secret when prompted.
  4. Upload your data. Use the AWS CLI or your preferred S3 client to upload your CSV files to the S3 bucket provided by Fraudio.
  5. Confirm the upload. Check the S3 bucket and confirm that all files are present. You can use the AWS Management Console or the CLI to list the files.
  6. Notify Fraudio. When the upload is complete, tell your Fraudio representative so processing can start.

Batch Integration​

At Fraudio, we specialize in real-time transaction fraud monitoring through our API. This integration allows you to inform us of transactions as they occur, enabling prompt fraud identification, AI adaptation for future transactions, and bolstering our fraud detection capabilities.

While we strongly recommend the real-time API integration for its simplicity and effectiveness, we recognize that certain circumstances may necessitate alternative solutions. Factors such as resource constraints or technical infrastructure limitations could impede real-time integration.

To accommodate these situations, we offer an alternative method: batch transfer integration. This approach entails uploading files on a scheduled basis rather than transmitting data in real-time via the API.

With this method, you can upload new files at a regular interval, which will be automatically imported into our systems. This ensures that our platform can continue to provide timely and efficient fraud detection and prevention.

Comparison: API integration and batch integration​

API IntegrationBatch Integration
Large amounts of data at oncenoyes
Programming effortmediumlow
Encrypted by defaultyesyes
Transaction fraud detection periodsub-secondsdays
Merchant fraud detection periodless than a daydays
Data quality reportingAutomaticOn Request
ProtocolHTTPSS3
FormatJSONZipped CSV
AuthenticationAPI TokenKey ID + Secret
Maximal no. of scored transactions per dayno limit10.000.000 (soft limit)