The processor authorized the transaction. Your customer may see a pending charge on his or her account. However, before the customer is actually charged and before you receive the funds, you must submit the transaction for settlement. If you do not want to settle the transaction, you should void it to avoid a misuse of authorization fee.
The transaction spent too much time in the Authorized status and was marked as expired.
- American Express authorizations will be marked as expired after 7 days.
- Visa and Mastercard authorizations will be marked as expired after 10 days.
- All other authorizations will be marked as expired after 30 days.
The processor declined the transaction. The processor response code has information about why the transaction was declined.
An error occurred when sending the transaction to the processor.
If the transaction is Settling or Settled, you will have to refund the transaction instead.
The transaction has been submitted for settlement and will be included in the next settlement batch. Settlement happens nightly – the exact time depends on the processor.
The transaction is in the process of being settled. This is a transitory state. A transaction cannot be voided once it reaches Settling status, but can be refunded.
The transaction has been settled.
The processor declined to settle the sale or refund request, and the result is unsuccessful. This can happen for a number of reasons, but the processor settlement response code may have more information about why the transaction was declined. This status is rare, and only certain types of transactions can be affected.
- PayPal sale: We recommend checking the settlement status of all PayPal sale transactions before shipping goods or providing services to customers. To reduce these types of declines, submit your PayPal transactions for settlement either upon creation or within 3 days of creation.
- PayPal refund: We recommend contacting PayPal for details on refunds that are Settlement Declined.
- Credit card refund: Settlement declines can be hard or soft, just as with authorizations. In regions that support an immediate decline response for refunds, we will return Settlement Declined if the processor responds with a hard decline.
The transaction has not yet fully settled. This status is rare, and it does not always indicate a problem with settlement. Only certain types of transactions can be affected.
- PayPal sale
- If using multiple partial settlements: Settlement Pending is a normal part of the transaction flow. The parent authorization will remain in this status until all child transactions are settled or the authorization expires. See the multiple partial settlement reference for more details.
- If not using multiple partial settlements: Almost all Settlement Pending PayPal transactions will settle without intervention, so we always return a successful result. In general, you can expect these to be updated to Settled within a few days as we confirm their status with PayPal. In the rare case we cannot settle a Settlement Pending transaction, we'll contact you to resolve the issue.
- Credit card, Android Pay, and Apple Pay sales: You will only see Settlement Pending authorizations if you have contacted us to enable a specific API feature that uses this status.
The processor declined the verification. The processor response code has information about why the verification was declined.
An error occurred when sending the verification to the processor.
The card was verified successfully by the processor.
These statuses are only for Braintree Marketplace merchant transactions.
The transaction will be held in escrow once settled.
The transaction has settled and is now held in escrow and eligible to be released.
The transaction being held in escrow will be released and disbursed shortly.
The transaction that was being held in escrow has been released.
The transaction that was being held in escrow has been refunded. Only full refunds are allowed for escrow transactions.
Pending subscriptions are subscriptions that have not started yet. For example, if you create a subscription with an explicit first bill date or a specific billing day of month that is in the future, the subscription will start out as Pending.
Active subscriptions will be charged on the next billing date. You can get the dates from the subscription object. Subscriptions in a trial period are Active.
If a payment for a subscription fails, the subscription status will change to Past Due. You can manually retry the charge, or you can set up logic in the Control Panel to automatically retry a declined or failed charge at specific intervals. Additionally, a past due subscription will be automatically retried if the payment method associated with the subscription is updated and you either have proration enabled or are manually passing the prorate charge option. If the retried transaction is successful and the subscription has not passed its last billing date, the status will change to Active.
If a retried transaction is unsuccessful, the balance on the past due subscription will continue to increase every billing cycle, and we'll continue to retry the transaction each billing cycle—either indefinitely or until the number of cycles in the subscription is reached. If all retries are unsuccessful, the subscription’s status will remain Past Due until the subscription a) reaches the specified number of billing cycles and the status changes to Expired, or b) is canceled.
Subscriptions are Expired when they have reached the specified number of billing cycles.
If you cancel the subscription, the status will be Canceled and no further billing will occur.
Still have questions?
If you can’t find an answer, contact our Support team.