Best Practices for eCommerce API Payments
Whether you’re using Square’s API or one of our partners, accepting eCommerce payments is great way to establish or grow your business. It’s also important to take additional precautions on these types of orders to prevent fraud and disputes. Even a successful transaction could be from a payment card that hasn’t yet been reported as stolen or compromised.
Be Cautious of Requests for Immediate or Expedited Delivery###
Additionally you can check to see if the shipping address is a private address. Mail drop-off locations, such as DHL or UPS offices, and freight forwarders, are commonly associated with fraud and we do not recommend shipping to them.
If you’re shipping a product, make sure to keep the tracking information and a delivery receipt. For large orders, require a signature confirmation at delivery.
Monitor Declined Cards###
Declined cards can be a sign that someone is trying to pay using stolen payment card information. If you notice an order with mismatched billing and delivery information, review possible attempts to use multiple cards by logging into your Dashboard, selecting Sales > Transaction Status. If a customer attempted to pay with multiple cards within a short time frame, refund the successful payment.
eCommerce Platform Merchants###
Third party eCommerce platforms (such as Bigcommerce, Weebly and Ecwid) may offer additional solutions such as Signifyd to minimize your risk. While we currently don’t offer this option, you may be able to find a solution on these platforms that works best for your business.
eCommerce API Merchants###
If you’re using the developer API, consider passing additional information to Square about your orders such as buyer email addresses and delivery information. More order details help us better protect you.