---
title: How Order Data Is Built and Mapped
slug: extensions/how-order-data-is-built-and-mapped
docTags: 
createdAt: 2026-09-22T18:20:22.602Z
---

By default, the cartridge sends Forter a raw snapshot of the order, customer, and payment data, plus a few derived fields (past-order count, product categories). Forter maps this to its own schema server-side. The cartridge does no PSP-specific field mapping in this path. It reads payment fields generically across any processor.

This mapping runs through a per-merchant template that your Forter implementation team deploys during onboarding — see [Prerequisites](https://docs.forter.com/extensions/prerequisites). The same mapper also extracts additional data from a PSP's raw response when one is passed through. See [PSP Integration Guide](https://docs.forter.com/extensions/psp-integration-guide).

A fixed set of sensitive fields is excluded before sending. See [Privacy](https://docs.forter.com/extensions/privacy).

## Legacy order format

`forterEnableLegacyOrderRequest` (off by default) switches to an older, pre-structured order format instead. This format is hardcoded for Authorize.Net. Enabling it on any other payment processor will send broken or missing payment data. Leave this disabled unless Forter instructs otherwise.