Pull Transactions


The following documentation explains requirements for Evolve’s Pull Transaction solution.

The Point of Sale (POS) and eCommerce solution represents a traditional card purchase transaction (or Pull transaction). In this card acquiring processing solution, the end user's card and verification data are collected by the Platform and used to initiate a pull transaction across one of the card networks. The card data and verification can be collected from a POS system or an eCommerce application.

Network Fees

The network fee only applies to PULL transactions. They do not apply for PUSH transactions.

In order to avoid network fees on transactions for integrity reasons, here are some tips:

  • Keep bad actors out
  • Have checks in place to prevent re-use of PANs when they are used by "suspicious" accountholders
  • Do not re-try transactions that have been errored out by the network esp those involving lost or stolen cards

Excessive Retrieves

To avoid negative impacts to cardholders and the processing systems caused by erroneous authorizations that are not authorized, reversed or cleared according to their requirements, card networks Visa and Mastercard have integrity programs to promote good behavior. Visa's Processing Integrity Fee program and Mastercard's Transaction Processing Excellence.

In a concerted effort to promote and maintain these good authorization practices prescribed by the networks, Evolve requires all integrating customers are aware of these integrity programs, adhere to them, and understand the implications with avoidance of these programs.

Additional Best Practices

  • Avoid repeated authorizations when you encounter a failure. Retrying multiple angles through which the transaction can go through may result in integrity fees.
  • Widen fraud mitigation programs. Fraudsters are notorious for triggering repeated transactions when they are in possession of a lost or stolen card. Evolve strongly recommends implementing our fraud programs:
    (1) AVS/CVV2 Check
    (2) EMV 3DS
    (3) Duplicate Card Check
    (4) Anti-money Laundering controls
  • Implement front-end mitigation programs especially those that are programmatic in nature and ensure repeat authorizations regardless of failure. Anti-spam programs like CAPTCHA on your user experience flows can help avoid a robotic attack, for instance.
  • Understand your end users; guide them through their user experience as they interact with your application.
  • Avoiding clicking on Submit button for instance could stop triggering an additional transaction.
  • Get consumer consent: For consumer transactions, it is important to get consumer consent before placing a transaction request.
  • Send notifications: Try notifying the verified customer phone number or email on your file prior to initiating transactions