CARE API Overview
3 min
\<font color="#b6c7cb">\</font> topic type concept purpose api overview, request vs settlement flows, and integration scope audience api integrators and client developers implementing transactions applies to clients using the api for claims, adjustments, refunds, returns, and exchanges via api does not apply to retail/fraud industry apis or clients using non api integrations the api lets you send requests and settlements to the to address risk associated with claims, adjustments, refunds, returns, and exchanges the api gets you up and running quickly, validates the data you send, and lets you leverage all the data associated with your original transactions if accepts the data you send, it creates a new transaction or updates an existing transaction if rejects the data you send, it returns detailed warning and error messages in the response how works you send us api inputs when you finalize the settlement of a claim, adjustment, return, refund, or exchange we create a record for the settlement in the and track customer data overtime using keys (email address, shipping address, and so forth) you use the aggregated stats in rules to approve or deny the next transaction using those keys in between steps one and two above, your event data is processed through our system we measure consistency and change in the data collected compared to previous requests and that customer's original transactions, and push it through the two processing flows requests and settlements supports two data flows for transactions requests and settlements when coding, requests differ from settlements in that they include device fields request transactions occur when a user attempts to process a related action on your website, and you must decide whether to grant the request care request flow settlement transactions occur when your agent processes a transaction (for example, a reship), and you must decide whether to allow that customer’s next transaction care settlement flow calling the api the api request must come from a backend server javascript submission is not supported due to backend data requirements, event specific error handling, ip allowlisting, and hashing requirements for certain fields field reference view field requirements, paths, and try it out! us request fields https //atlas accertify com/public apis/dkkk care request us settlement fields https //atlas accertify com/public apis/yssg care settlement eu request fields https //atlas accertify com/public apis/mjji care request eu eu settlement fields https //atlas accertify com/public apis/5v7q care settlement eu