Wrong Payment Account Was Used to Capture Payment

Wrong Payment Account Was Used to Capture Payment

Module: Payment Processing
Topic: Wrong Payment Account Was Used to Capture Payment
Version(s): 5.1 & up
Editions: All

Wrong Payment Account Was Used to Capture Payment

When an order is placed without a preauth, the first filter of payment processing is the schedule that runs first and then if it is set up to override Pay Proc Acct Campaign/Product group constraints. If the order is placed and receives a preauth during order creation, the payment can only be settled under the account the preauth was created in. This will be the payment account associated to the script, OR if imported, the payment account associated to the job or xml, OR if a token is used, the account the token was created under.

First things to check when an order is processed under the wrong account is:
  • is there a preauth
    • yes
      • was a token used
        • yes
          • what account is the token associated to?
            • is this the account order processed under
              • yes
                • stop - this is the reason
                • it is possible the first card declines, and a new card es added which inherently uses the same PPA as the former tokenized card
                • orders automatically get assigned to PPA associated to payment profile selected from customer record if profile is a token - regardless of if payment is updated during order creation
              • no
                • create ticket
        • no
          • was the order created via
            • manual
              • what ppa is on the script associated to the source used? MAKE SURE YOU ARE LOOKING AT INACTIVE SOURCES AS WELL
                • is this the account order processed under
                  • yes
                    • stop - this is the reason
                  • no
                    • was the script modified after order was placed?
                      • yes
                        • stop - this is the reason
                      • no
                        • create ticket
            • import
              • what ppa is associated on job
                • is this the account order processed under
                  • yes
                    • stop - this is the reason
                  • no
                    • create ticket
              • what ppa is on the xml
                • is this the account order processed under
                  • yes
                    • stop - this is the reason
                  • no
                    • create ticket
    • no
      • is realtime auth set to true on the script associated to the source used? MAKE SURE YOU ARE LOOKING AT INACTIVE SOURCES AS WELL
        • yes
          • was script updated after ticket was created
            • yes
              • stop - this is the reason
                • realtime auth had to have been set to false when order was created, due to there not being a preauth on the order
            • no
              • create ticket
        • no
          • is the "wrong account" scheduled to run before expected payment account, and does it have override constraint checked?
            • yes
              • stop - this is the reason
            • no
              • what account is default on product group
                • is this the account order processed under
                  • yes
                    • stop - this is the reason
                  • no
                    • review campaign
              • what account is default on campaign
                • is this the account order processed under
                  • yes
                    • stop - this is the reason
                  • no
                    • create ticket

Copyright 2025
Revised 7.16.2025