SFCC Reference Architecture

the cartridge integrates via sfra hooks and controller extensions sfra's base controllers and templates are never modified the two cartridges cartridge role int forter sfra core storefront integration — hooks, controller extensions, dtos, services, the device fingerprint template, and the order status sync job bm forter business manager extension — credential verification, order search by forter decision, abuse policy configuration, account protection settings hooks ( hooks json ) hook script purpose app template afterfooter templatehooks js device fingerprint js injection app validate order validateorder js pre authorization fraud decision app post auth postauthorizationhandling js post authorization fraud decision, plus pre auth decision mirror onto the order app payment saved paymentsavedhandling js payment save capture for psp flows that bypass the standard save payment route beyond the hooks controller extensions for account protection events — account js , address js , paymentinstruments js — extend the base sfra controllers dtos ( scripts/lib/forter/dto/ ) — the cartridge sends a raw snapshot of the order/customer; forter maps it to its canonical schema server side order status sync job ( forterorderupdatesfra ) — a scheduled job that reports lifecycle changes (shipped, cancelled, refunded) back to forter asynchronously