SecureSubmit Gateway error when processing a stored credit card

When processing a payment that is using a credit card that is stored in the system, the following error displayed:

SecureSubmit Gateway: Transaction rejected because the lookup on the supplied token failed.  TaaS ResultCode:  400

Brandon at Heartland advised: 

You typically get that error when the single use token expired before being used (only good for 30 minutes), or because the public key it was generated on doesn't match the private key (or username/password) that you are trying to authorize a sale with.

• Related Articles

• Mobile Error 1033

  Unable to connect via Mobile and receiving Error 1033. Tunneling was not running. Restarted Tunneling and could connect to Mobile again.

• Security Pre-Authorization versus Security Deposit

  When taking a credit card payment, it can be taken as a Payment, a Security Pre-Auth, or a Security Deposit. - Payment: A Payment will charge the customer's credit card and will reduce the Amount Due on the Order. - Security Pre-Auth: A Pre-Auth is a ...

• How Do You Credit Delivery / Pickup Charges?

  Steps to issue a credit for Delivery / PickUp Charges Front Counter > Credits > New Credit Select the transaction to be credited > Next Line by Line > Next Click on Header Credits Select the Delivery or Pickup Charge option Save Continue as you ...

• Depreciation - Set up and Processing

  Depreciation Set Up 1) Configuration > Depreciation Types > In the Depreciation Types File, set up the different depreciation methods used and for the periods depreciated. i.e., Straight Line - 5 Years, MACRS - 3 Year, etc Description: will display ...

• Adjusting Tax Situations

  1) Tax was charged on an Order and now you have the Tax Exempt ID Number / should not charge tax. Front Counter > Credits > New Credit > enter the Order Number > Tax Only > Enter the Tax Exempt ID > Next > following screens through to complete the ...