Article ID: 117295, created on Sep 16, 2013, last review on May 11, 2014

  • Applies to:
  • Business Automation 5.4

Symptoms

As Provider I want to configure PBA to notify customers about events related to processing of their credit card payments. The events may include the following ones:

  • Credit card has been charged
  • An attempt to charge a credit card has failed
  • Preauthorization of a credit card has failed
  • Credit card preauthorization has successfully completed

Resolution

Notification for failed credit card charges can only be configured from the Order Flow in PBA. The request PBA-43924 to make it possible to configure notifications from event handlers was already submitted.

Follow the steps below to configure notifications in the Order Flow of the Payment Order (the Payment Order is chosen because all the payment transitions are present in its Order Flow):

  1. Create new notification template in PBA Provider Control Panel at Communication Director > Notification Manager > Notification Templates

    Message type needs to be set to "Order Notification".

  2. Configure the notification to be sent in the Order Flow of the Payment Order:

    1. Go to Configuration Director > Order Processing > Order Flow
    2. Click on the Payment Order
    3. Switch to the Order Flow Transitions tab
    4. In the 'CA -> CF/WT' transition set the created notification template in the 'Success Template Name' field

      So, when the the number of possible attempts to charge customer's credit card will be exceeded, the customer will receive the notification indicated.

    5. In the 'CC -> PP/CA' transition configure PBA to send 'charge failed' notifications on each failed attempt to charge credit card - set the created notification template in the 'Fail Template Name' field.

    6. Review the rest existing transitions and choose those you would like to notify your customers about.

Search Words

failed credit card notifications

failed payment notification

failed CC notifications

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 210d017ddc3a076d22f0f865b1cf0730 92711db0799e8aefe8e51f12dace0496 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF