Agentic Orders

when a merchant receives an order from a consumer's agent (e g chatgpt or gemini), they should call the forter api with additional data, signaling forter the transaction source as well as transaction metadata provided to the merchant by the agent this additional data improves forter's risk decisions and provides the merchant better reporting on agentic traffic fortertokencookie & fortermobileuid in agentic flows, forter's javascript snippet and mobile sdk are typically not present, meaning fortertokencookie and fortermobileuid will not be available this is expected forter's system is adapted to assess agentic transactions with the data provided through the fields below ordertype set ordertype to ai agent additionalidentifiers add the additionalidentifiers agenticcommerceplatform object with the following fields agentsourcetype usually the vendor or ai company which can operate multiple platforms (e g openai) agentplatform the flow or product of the ai agent application (e g chatgpt instant checkout) agentapp use if the platform is not available in the agentplatform list, or when you need to further segment the channel, traffic or orchestrator (e g , paypal acs) agentid a unique identifier provided by the ai agent orchestrator or platform the following platforms are currently supported additional platforms will be added as they become available agentsourcetype agentplatform openai chatgpt instant checkout , chatgpt agent , chatgpt apps sdk google search , ai mode , gemini microsoft copilot perplexity buy with pro amazon alexa , buy for me meta ads third party gensmo , other in house henrylabs connectioninformation populate connectioninformation customerip with the end user's ip address (if available) google's ucp has it under signals dev ucp buyer ip populate connectioninformation useragent with the full, end user's agent google's ucp has it under signals dev ucp user agent payment for google ucp orders, map the selected payment instrument from the ucp payment instruments\[] array (the entry where selected is true ) for google ucp using google pay, use forter's payment androidpay object given the following ucp instrument "payment" { "instruments" \[ { "id" "pi gpay 5678", "handler id" "gpay 1234", "type" "card", "selected" true, "display" { "brand" "mastercard", "last digits" "5678", "card art" "https //cart art 1 html", "description" "google pay •••• 5678" }, "billing address" { "street address" "123 main st", "address locality" "anytown", "address region" "ca", "address country" "us", "postal code" "12345" }, "credential" { "type" "payment gateway", "token" "examplepaymentmethodtoken" } } ] } map the fields as follows display brand → cardbrand display last digits → lastfourdigits credential token → token credential type → tokentype resulting in the following forter payment androidpay object "payment" { "androidpay" { "cardbrand" "mastercard", "lastfourdigits" "5678", "token" "examplepaymentmethodtoken", "tokentype" "psp" } } when the payment instrument is not google pay, send it through the matching payment object instead (e g creditcard , tokenizedcard , applepay ), mapping the available non pci fields from the agentic payload into the corresponding forter fields the bin and expiration are often missing from agentic payloads when they are, try to retrieve them from your tokenizer or psp service api additionalinformation as protocols continue to evolve, please add the following payloads as they become available for google include the ucp signals as ucpsignals for openai include the acp signals as acpsignals for adyen include adyen signals as adyensignals for paypal include paypal signals as paypalsignals for stripe include stripe signals as stripesignals schema your api schema should be set to support this additional fields and/or make some of the missing ones optional if it isn't, contact your forter implementation engineering team to get it updated api reference https //portal forter com/app/integration/docs/api reference?api=validation#request additionalidentifiers agenticcommerceplatform