Retail API Overview
3 min
\<font color="#78b5c7">\</font> topic type concept purpose retail api overview, differences, and hashing requirements audience api integrators and client developers applies to retail clients implementing via api does not apply to any other industry or retail clients who opt for a non api integration the retail api is designed for transactions involving consumer goods and fulfillment‑oriented purchases , built on the shared core model (transaction, account, payment, items, addresses, device signals, and so forth) 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 if your implementation can supply an imperative field, you should send it consistently 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 api fields https //atlas accertify com/public apis/us retail path view field requirements, paths, and try it out!