SaaS

Enhancing your disputes with essential order data is critical to increasing your win rate. The Chargeflow Public API simplifies this process, ensuring the submissions are comprehensive and impactful.

In addition to standard buyer order information—service details, price, quantity, and confirmation URL—our API also gathers the required data per the card schemes’ requirements. This includes:

• Subscription Information (if applicable): Charge history (subscription[].chargeHistory[]), frequency (subscription[].frequency), and status (subscription[].status).

• Customer Activity Logs (customer.activity): Detailed records of events demonstrating the customer's engagement with your service and awareness of their purchase; here are some examples:

  Event	Explanation	Importance
  Sign up	This event includes customer sign-up data for the merchant's website, including timestamp, IP address, etc.	It helps to prove that the customer is familiar with the merchant and its service/product.
  Login	This event includes customer login data for the merchant’s website, including timestamp, IP address, etc.; it is beneficial to send multiple login events.	It helps prove that the customer has intentionally used the merchant’s service/product.
  Purchase	This event includes customer purchase data of the service/product from the merchant's website; it is beneficial to send multiple purchase events, if available.	Strengthen the case by claiming the customer knows the merchant, the service/product quality, and authorized the transaction.

• Customer Communication: A screenshot of the conversation with the buyer to prove you adhere to your SLA and that the customer knows about their purchase, using our POST Upload Evidence API.

By focusing on these key areas, our automation system crafts a powerful rebuttal on your behalf, significantly boosting your chances of winning disputes and recovering revenue.