Skip to main content

Update a payment method or fix a failed payment

Find the payment details for your plan and resolve access or payment errors without paying twice.

Written by Elon Datt

Start with Settings > Manage Plan in the Tapt Dashboard to review the linked payment method, if one is shown. Check the purchasing email too, especially if a payment update sends a message to that address.

​


Update the payment method

  1. Sign in to the Tapt Dashboard and open Settings > Manage Plan.

  2. Review the linked payment method and purchasing email.

  3. Use the payment-update option available for your account, if shown, and follow its instructions.

  4. Complete any requested verification using the correct purchasing inbox.

  5. Check for confirmation that the new method has been saved.

If you cannot find an update option or cannot access the purchasing inbox, contact Tapt Support. Include the organisation name and explain which step is blocked.

Provide payment details only through the payment form supplied for your account. Do not email a full card number or security code.

​


Check a failed payment

  • Review the failure message and invoice reference.

  • Check that the payment details you entered are correct and current.

  • Check with your bank if it declined the transaction or requires approval.

  • Look for a payment confirmation or bank transaction before trying again.

If the payment appears in your bank account but Tapt still shows it as outstanding, ask Tapt Support to reconcile it before paying again.

​


Confirm the outstanding invoice is settled

Saving a new payment method is not evidence that an existing invoice has been paid. Check the payment confirmation and ask Tapt Support whether a further payment action is required.

For help, provide the invoice number, payment date, amount, reference and the error shown. For a bank transfer, include the relevant remittance confirmation without unrelated bank information.

If payment succeeded but access remains blocked, use the overdue-platform-fee troubleshooting guide.

Did this answer your question?