Statuses

• Your customer initiated a transaction, but abandoned it by closing his browser window.
• Your customer initiated a transaction, but is not yet done (i.e. the customer is currently entering his credit card data or we are waiting for a response from the acquirer).

• Have a look at our Tips to maximise conversion with your payment page guide to improve your conversion rate!
• Contact your customer to know more about the abandoned transaction.
• As soon as the customer has finished entering their card details and we have received a response from the acquirer, we will update the status. Depending on your acquirer's response and the action performed on the transaction (authorisation only vs. authorisation and data capture in one step), we will update the transaction to one of the following statuses:
  
  • statusOutput.statusCode=2 (Authorisation refused)
  • statusOutput.statusCode=5 (Authorised)
  • statusOutput.statusCode=9 (Payment requested)

• Your customer has cancelled the transaction by hitting the "Cancel" button on the Hosted Checkout Page or in the portal of a third party payment service provider (i.e. PayPal).

• This is a final status. No further actions are possible.
• Have a look at our Tips to maximise conversion with your payment page guide to improve your conversion rate!
• Contact your customer to know more about the abandoned purchase.

Oops! Your acquirer declined the authorisation due to:

• Unsuccessful/missing 3-D Secure check by your customer.
• Your customer does not have enough funds to make the purchase.
• The MIDs used for the payment method configured in your account is not correctly setup.
• Your Fraud Prevention module has rejected the transaction due to suspicion of fraud.

• This is a final status. No further actions are possible.
• Your customer can retry the authorisation process after selecting another card or another payment method.
• Contact us to ensure that your MIDs are correctly setup on our platform/at your acquirer.

This is an intermediate status for transactions:

• for which the 3-D Secure check has yet to begin or is not finished yet.
• for which your customers have been redirected to a third party (i.e. PayPal, Multibanco, Klarna, Bizum) to complete the payment.

• Depending on the integration mode you use, three scenarios are possible leading to this status:
  • Hosted Checkout Page: After entering the card number on our secure payment page, our platform automatically redirects your customer to her/his issuer to perform the 3-D Secure check.
  • Hosted Tokenization Page / Server-to-server: After sending a CreatePayment request with a 3-D Secure enrolled card that triggers a challenge flow, our platform sends a response containing a MerchantAction object. Its property MerchantAction.ActionType=REDIRECT indicates that you have to redirect your customer to her/his issuer.
  • Your customers have been redirected to the payment portal of a third party or we have not received a transaction result from this third party yet.

• If you have sent the request via Hosted Checkout Page, our platform take care of the redirection to the issuer automatically.
• If you have sent the request via either Hosted Tokenization Page / Server-to-server, proceed as described in our documentation to redirect your customer to her/his issuer.
• For transactions processed by a third party, our platform will update the transaction to a final status once your customers have completed the payment.
• Depending on your acquirer's response and the action performed on the transaction (authorisation only vs. authorisation and data capture in one step), we will update the transaction to one of the following statuses:
  
  • statusOutput.statusCode=2 (Authorisation refused)
  • statusOutput.statusCode=5 (Authorised)
  • statusOutput.statusCode=9 (Payment requested)
• The transaction will remain in this status until your customer has finished the authentication check/completed the payment on the third party portal. If your customer abandons the 3-D Secure check prematurely (i.e. by closing the browser window), the transaction will remain in statusOutput.statusCode=46 indefinitely.

Congratulations! Your authorisation request has been accepted. The funds have been reserved on your customer's card.

• You initially processed the transaction as an authorisation. 

• Make sure you capture the transaction to collect your funds. The subsequent status will be statusOutput.statusCode=91 
• You can also decide to cancel the authorisation by performing one of the following actions. The subsequent status will be statusOutput.statusCode=61 (Author. deletion waiting).

Our fraud team is currently validating your transaction.

• Until the fraud validation is finalised, the transaction will remain in status 50. This process usually takes less than 5 hours to complete.

• This is a temporary status. No further actions are needed. Depending on your acquirer's response and our fraud team's validation, we will update the transaction to one of the following statuses:
  
  • 2 - Authorisation refused
  • 5 - Authorised
  • 9 - Payment requested

Your authorisation request is temporarily pending. We are waiting for your acquirer's answer.

You opted for offline authorisation request and not in real-time.

• You have configured your account to process transactions offline when the online acquiring system is unavailable or always offline. Contact us if you want to change that.
• Regardless of the settings described above, certain payment methods are processed offline, which makes this the default result for authorisation requests.

• This is a temporary status. No further actions are needed. Depending on your acquirer's response, we will update the transaction to one of the following statuses:
  
  • statusOutput.statusCode=2 (Authorisation refused)
  • statusOutput.statusCode=5 (Authorised)

• Oops! A technical problem occurred during the payment authorisation or payment request to your acquirer, leading to an unknown status. The actual result is temporarily unclear.

• As your initial request might have been successful., please do not resend the initial request. This is to avoid double bookings of the same order.
• Although we will recover the status within a few hours, you may contact your acquirer yourself to learn the actual result.
• Depending on the value for property cardPaymentMethodSpecificInput.authorizationMode sent in your CreatePayment/CreateHostedCheckout request, we will update the transaction to one of the following statuses:
  • Authorisation / "FINAL_AUTHORIZATION"/"PRE_AUTHORIZATION":
    statusOutput.statusCode=5 (Authorised) or statusOutput.statusCode=2 (Authorisation refused)
  • Direct Sale / "SALE":
    statusOutput.statusCode=9 (Payment requested) or statusOutput.statusCode=2 (Authorisation refused)
    
    

• Great! You successfully deleted the authorisation of a transaction.
  
  

• This is a final status. No further actions are possible.

• You requested to cancel the authorisation of a transaction. As we are waiting for a response from your acquirer, your transaction is in a pending status.

• This is a temporary status. No further actions are needed.
• Depending on your acquirer's response, we will update the transaction to one of the following statuses:
  • statusOutput.statusCode=6 (Authorised and cancelled)
  • statusOutput.statusCode=63 (Author. deletion refused)

• Oops! A technical problem occurred during your authorisation cancellation request, leading to an unknown status. The actual result is temporarily unclear.

• This is a temporary status. No further actions are needed. Depending on your acquirer's response, we will update the transaction to one of the following statuses:
  
  • statusOutput.statusCode=6 (Authorised and cancelled)
  • statusOutput.statusCode=63 (Author. deletion refused)
• Although we will recover the status within a few hours, you can contact your acquirer yourself to learn the actual result.

• Great! The payment deletion request for a transaction that has just recently received statusOutput.statusCode=9 has been successful.

• This is a final status. No further actions are possible.
• Thanks to your action, you will prevent the acquirer to effectively payout the funds of the impacted statusOutput.statusCode=9 transaction.

• You requested to delete a payment (a refund request for a transaction that has just recently received statusOutput.statusCode=9). As we are waiting for a response from your acquirer, your transaction is in a pending status.

• This is a temporary status. No further actions needed.
• Depending on your acquirer's response, we will update the transaction to one of the following statuses:
  • statusOutput.statusCode=7 (Payment deleted)
  • statusOutput.statusCode=73 (Payment deletion refused)

• Oops! A technical problem occurred during your payment deletion request (a refund request for a transaction that has just recently received statusOutput.statusCode=9), leading to an unknown status. The actual result is temporarily unclear.

• This is a temporary status. No further actions are needed. Depending on your acquirer's response, we will update the transaction to one of the following statuses
  • statusOutput.statusCode=7 (Payment deleted)
  • statusOutput.statusCode=73 (Payment deletion refused)
• Although we will recover the status within a few hours, you can contact your acquirer yourself to learn the actual result.

• Oops! Your acquirer declined your payment deletion request (requesting a refund for a transaction that has just recently received statusOutput.statusCode=9).

• This is a final status. No further actions are possible.
• Please check with the acquirer to learn about the exact reasons for the decline.

• Great! We successfully refunded your payment

• This is a final status. No further actions are possible.

• You requested to refund a payment. As we are waiting from your acquirer for a response to your request, this transaction is in a pending status

• This is a temporary status. No further actions needed.
• Depending on your acquirer's response, we will update the transaction to one of the following statuses
  • statusOutput.statusCode=8 (Refund)
  • statusOutput.statusCode=83 (Refund refused)

• Oops! A technical problem occurred during your refund request, leading to an unknown status. The actual result is temporarily unclear.

• This is a temporary status. No further actions are needed. Depending on your acquirer's response, we will update the transaction to one of the following statuses
  
  • statusOutput.statusCode=8 (Refund)
  • statusOutput.statusCode=83 (Refund refused)
• Although we will recover the status within a few hours, you can contact your acquirer yourself to learn the actual result

• Oops! Your acquirer declined your refund request.

• The global status of the transaction will remain in statusOutput.statusCode=9 (Payment requested). Therefore, you can retry the operation at a later point. Before you do so, please check with your acquirer why your initial request has been declined to avoid subsequent denials

• The transaction was paid back to the customer due to a chargeback. It is possible a fraudster used the credit card details of the customer.

• This is a final status. No further actions are possible.
• Consult our Fraud Prevention to prevent chargebacks like this from happening in the future.

Congratulations! Your CreatePayment/CapturePayment request has been successful. You can expect the funds to be paid out to you.

• You initially processed the transaction via a direct sale request or captured the initially authorised amount. 

• You can refund the payment to your customer anytime. Depending on whether your acquirer has already transferred funds or not at the time of the refund request, the payment will be either refunded (statusOutput.statusCode=81) or deleted (statusOutput.statusCode=71) respectively.

• You requested to confirm an authorisation request. As we are waiting for a response from your acquirer, this transaction is in a pending status.
• This is the follow-up status of a statusOutput.statusCode=5 (Authorised).
• The acquirer needs to check whether the initial authorisation can still be captured.

• This is a temporary status. No further actions needed.
• Depending on your acquirer's response, we will update the transaction to one of the following statuses:
  • statusOutput.statusCode=9 (Payment requested)
  • statusOutput.statusCode=93 (Payment refused)

• Oops! A technical problem occurred during your authorisation/payment request, leading in an unknown status. The actual result is temporarily unclear.

• This is a temporary status. No further actions needed.
• As your initial request might have been successful, please do not resend the initial request. This is to avoid double bookings of the same order.
• Depending on your acquirer's response, we will update the transaction to one of the following statuses:
  • statusOutput.statusCode=9 (Payment requested)
  • statusOutput.statusCode=93 (Payment refused)
• Although we will recover the status within a few hours, you can contact your acquirer yourself to learn the actual result.

• Your acquirer declined your data capture request.

• The global status of the transaction will remain in statusOutput.statusCode=5. Therefore, you can retry the operation at a later point. Before you do so, please check with your acquirer why your initial request has been declined to avoid subsequent denials.

• This is a temporary status which appears only when the status transition from one status to another is interrupted.

• This is a temporary status. No further actions are needed.
• If you have transactions that remain in this status for more than than 5 minutes please contact us.