All authorizations expire, though the timeframes differ by payment method. This is a common challenge for businesses that wait to collect funds until they are ready to ship their products or provide their services. Below are some options and limitations to be aware of when managing your authorization workflow.


For PayPal transactions, delaying settlement for shipped goods isn’t necessary thanks to Seller Protection.

Authorization options

Merchants in some industries may want an authorization to stay active on a customer's account for longer than the timeframe established by the customer’s bank. There are two ways to do this in the Braintree gateway:

While we do recommend using the verify and store method, it’s up to you to decide what works best for your business.

Verify and store

To use the verify and store method, follow these steps:

  1. If the customer's payment method is a credit or debit card, use card verification to ensure that the card is valid; otherwise, continue on to the next step
  2. Store the payment method in the Vault
  3. Store the customer ID and/or payment method token in your business’s database
  4. When you’re ready to collect funds, create a transaction using the vaulted payment method


  • Little development work needed
  • May save you money in processing fees, compared to the multiple authorizations method


  • No guarantee that the customer will have sufficient funds at the time the transaction is created
  • No guarantee that the customer’s account will be active at the time of the transaction

Multiple authorizations


Because of the complications that this method can introduce to your customers and your developers, we don’t recommend it as a standard workflow.

If you decide that the multiple authorizations method is the best fit for your business, you will need to create logic on your end that identifies the payment method type from the details returned in a results object and then implement rules based on the payment method type’s expiration timeframe. Here’s a suggestion of what this logic could look like:

  1. Create a transaction to authorize the amount you plan to charge; do not submit for settlement yet
  2. Void the transaction within the appropriate expiration timeframe
  3. Create a new transaction to authorize the amount again; do not submit for settlement yet
  4. Repeat steps 2 and 3 if you need to continue to extend the authorization
  5. When you’re ready to collect funds, submit the latest transaction for settlement


  • Can guarantee that the customer has sufficient funds


  • Considerable development work needed
  • May cost more in processing fees
  • The voids may result in duplicate pending transactions on a customer’s account, causing confusion and preventing the customer from using those funds

Still have questions?

If you can’t find an answer, contact our Support team

← Back to Previous Page