Retail Extension Overview
4 min
\<font color="#78b5c7">\</font> topic type concept purpose legacy retail api overview, differences, and hashing requirements audience api integrators and client developers applies to legacy retail clients implementing via api does not apply to universal apis, any other industry, or retail clients who opt for a non api integration the universal retail api extends the universal fraud api shared transaction model for consumer goods, fulfillment oriented purchases, and retail payment workflows retail transactions use the same shared transaction structure as all universal fraud apis and add retail specific context such as line item, fulfillment, and delivery information retail extension model the universal retail api consists of shared transaction model account information payment information item information address information retail specific fulfillment context this approach allows retail integrations to share a common foundation with every other universal fraud api while preserving industry specific risk signals \<font color="#386b84"> note \</font> see retail complete request structure docid 72nokbq7aifqop5rgqtsp for the full path what makes retail different retail implementations typically emphasize line items (what was purchased, quantity, price, discounts) fulfillment and delivery context (shipping vs pickup patterns, address usage) payment method mix (single tender vs split tenders, wallet vs card, etc ) retail clients can vary significantly (product types, checkout flows, fulfillment models) this is why the field requirement model is important hashing requirements the retail api follows the platform hashing rules fields designated as hash required must be hashed before submission, including giftcardnumber hashedpassword see hashing requirements docid\ yughwvl8eon7vcgswpcd3 (constraint) and accertify hash algorithm docid\ rkik1lb6euuwsz3sxpce (reference) field reference retail pre authorization risk score docid\ mav bnx6guuayzixeubx2 retail post authorization risk score docid\ yoqgvrma9y5vvohbpvsfg retail fulfillment update docid\ th13bbm2nbjxgubj7y rk retail chargeback update docid alvm8fgbnjmncls whwt retail authorization update docid\ dytd5zaw4rfgbz2grgjsz