Different Hold-on-Card Strategies

Edited
  • Placing a hold on the Customers Credit card is a default charing strategy in the PodPlay system

  • In such situations where a different Hold-on-Card charing strategy is requested, PodPlay offers three options

    • Option 1, the default strategy, will put a hold on the Customer’s cc:

      • If a Customer signs up for something <6 days in advance (within a week), Stripe immediately puts a hold on their cc

      • If a Customer signs up for something >6 days in advance (more than a week out), Stripe waits to put a hold on their cc, and then puts a hold on their cc 24 hours before the Event or Reservation

        • The reason for the delay in placing a hold on the cc is the legal classification of the product type: sports entertainment, which states that holds on a cc cannot be pending for more than 7 days

    • Option 2, will:

      • Charge the Customer immediately if the Reservation or Event is >6 days in advance (more than a week out), and

      • Put a hold on the Customer’s cc if the Reservation or Event is <6 days in advance (within a week)

        • The value of this strategy is to properly prompt the Customer to complete a 3D Secure (3DS) payment protocol

          • The 3DS protocol is a commonplace fraud tool outside of the U.S., so all PodPlay International Clients will use Option 2 or Option 3, and cannot use Option 1

    • Option 3, will:

      • Charge the Customer immediately for all Reservation bookings and Event signups

        • The value of this strategy is that a Club can collect all revenues immediately, though there is a high change of revenue losses if the Club’s Customer-base has frequent cancellations (as cancellations would prompt a refund, thus losing the Stripe Fee)

  • If you want to change your Hold-on-Card strategy from one option to another, please ask your PodPlay Customer Success Manager for assistance.