How Order Data Is Built and Mapped

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 # the same mapper also extracts additional data from a psp's raw response when one is passed through see psp integration guide # a fixed set of sensitive fields is excluded before sending see 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