1. Introduction

Our platform returns for many of the API calls the status of your request. This covers both requests for creating a new transaction or for getting the current status of an already existing transaction.
In most cases, our platform returns an object containing three (nested) properties describing all possible scenarios in a human-readable form:

Check out the following chapter to learn more about these return values and what they mean.

2. Understand human-readable return values

To be on top of your transactions, it is important to understand the exact meaning of these human-readable return values. Depending on the respective API call and the transaction status, they tell you everything you need to know about the transaction’s status, errors and possible follow-up actions.

Property "status"

The following values apply for these API calls, webhooks and properties

• status: GetPayment/RefundPayment/GetRefunds/CapturePayment/GetCaptures
• payment.status: CreatePayment/CancelPayment/CompletePayment
• createdPaymentOutput.payment.status: GetHostedCheckoutStatus

Property "statusOutput.statusCategory"

The following values apply for these API calls, webhooks and properties

• statusOutput.statusCategory: GetPayment/RefundPayment/GetRefunds/CancelPayment/CompletePayment
• payment.statusOutput.statusCategory: CreatePayment
• createdPaymentOutput.payment.statusOutput.statusCategory: GetHostedCheckoutStatus

Property "statusOutput.statusCode"

The following values apply for these API calls, webhooks and properties.
Check out our dedicated chapter about the meaning of the numeric status for these API calls and properties:

• statusOutput.statusCode: GetPayment/RefundPayment/GetRefunds/CancelPayment/CompletePayment
• payment.statusOutput.statusCode: CreatePayment
• createdPaymentOutput.payment.statusOutput.statusCode: GetHostedCheckoutStatus

Property “status” (GetHostedCheckoutStatus)

The following values apply for exclusively for API call/property “status” (GetHostedCheckoutStatus):

Property "createdPaymentOutput.paymentStatusCategory" (GetHostedCheckoutStatus)

The following values apply for exclusively for API call/property “status” (GetHostedCheckoutStatus):

3. Understand possible outcomes

Every API call providing feedback has a specific range of possible values. Have a look at the possible property value combinations per API call:

GetPayment/CreatePayment

GetHostedCheckoutStatus

RefundPayment/GetRefunds

CapturePayment/GetCapture

CancelPayment

4. Understand numeric status codes

In contrast to statusCategory and status, property statusCode return an integer instead of a string. In conjunction with the string-based properties, statusCode gives you the full picture of the transaction’s status and thereby the right API call to use in any given scenario.

• Show Hide

  0 - Invalid or incomplete

  How did I get this transaction status?

  • 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)

  What's next?

  • 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)
• Show Hide

  1 - Cancelled by customer

  How did I get this transaction status?

  • 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) 

  What's next?

  • 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
• Show Hide

  2 - Authorisation declined

  How did I get this transaction status?

  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

  What's next?

  • 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
• Show Hide

  4 - Order stored

  How did I get this transaction status?

  • You are waiting for the customer's payment (Exclusively linked to the payment method SEPA Direct Debit). The customer's issuer will transfer the money to us. As soon as we have received the funds, we will transfer them to you

  What's next?

  • Once we have transferred the funds to you, we will update this transaction to Status 9 - Payment requested
• Show Hide

  46 - Waiting authentication

  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

  How did I get this transaction status?

  • 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

  What's next?

  • 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
• Show Hide

  5 - Authorised

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

  How did I get this transaction status?

  • You have sent property cardPaymentMethodSpecificInput.authorizationMode="FINAL_AUTHORIZATION" / "PRE_AUTHORIZATION" in your CreatePayment/CreateHostedCheckout request  

  What's next?

  • Make sure you capture the transaction to collect your funds. We offer multiple ways to do so:
    • Via the Merchant Portal
    • Use the API call CapturePayment
    • Have the transaction automatically captured by our system. Contact us to make sure of this
      
      The subsequent status will be statusOutput.statusCode=91 (Payment processing)

  • You can also decide to cancel the authorisation by performing one of the following actions:
    • Via the Merchant Portal
    • Use the API call CancelPayment
      
      The subsequent status will be statusOutput.statusCode=61 (Author. deletion waiting)

• Show Hide

  50 - Authorised waiting external result

  Our fraud team is currently validating your transaction.

  How did I get this transaction status?

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

  What's next?

  • 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

• Show Hide

  51 - Authorisation waiting

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

  How did I get this transaction status?

  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.

  What's next?

  • 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)
• Show Hide

  52 - Authorisation not known

  How did I get this transaction status?

  • 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.

  What's next?

  • 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)
      
      
• Show Hide

  55 - Standby

  How did I get this transaction status?

  • Your customer has completed a partial payment via a gift card payment method
    Your customer will make an additional payment to complete the transaction

  What's next?

  • This is a temporary status. No further actions are needed from your end. Our platform will automatically redirect your customer to our Hosted Checkout Page. They will be able to select any payment method you have activated in your account. Depending on your acquirer's response, we will update the transaction to one of the following statuses
    • statusOutput.statusCode=2 (Authorisation refused)
    • statusOutput.statusCode=9 (Payment requested)
  • If your customer does not complete the payment within 24 hours, we will automatically refund the payment  and update it to statusOutput.statusCode=8 (Refund)
  • If you have transactions that remain in this status for more than 24 hours, please contact us

• Show Hide

  6 - Authorised and cancelled

  How did I get this transaction status?

  • Great! You successfully deleted the authorisation of a transaction
    
    

  What's next?

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

• Show Hide

  61 - Author. deletion waiting

  How did I get this transaction status?

  • 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

  What's next?

  • 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)
• Show Hide

  62 - Author. deletion uncertain

  How did I get this transaction status?

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

  What's next?

  • 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.
• Show Hide

  63 - Author. deletion refused

  How did I get this transaction status?

  • Oops! Your  acquirer declined your authorisation cancellation request
  • Be aware that this is the standard response for some acquirers, as they do not process authorisation cancellation requests. Instead of cancelling authorisations they will let them expire.

  What's next?

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

  7 - Payment deleted

  How did I get this transaction status?

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

  What's next?

  • 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
• Show Hide

  71 - Payment deletion pending

  How did I get this transaction status?

  • 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

  What's next?

  • 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)
• Show Hide

  72 - Payment deletion uncertain

  How did I get this transaction status?

  • 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.

  What's next?

  • 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.
• Show Hide

  73 - Payment deletion refused

  How did I get this transaction status?

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

  What's next?

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

  8 - Refund

  How did I get this transaction status?

  • Great! We successfully refunded your payment

  What's next?

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

  81 - Refund pending

  How did I get this transaction status?

  • 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

  What's next?

  • 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)
• Show Hide

  82 - Refund uncertain

  How did I get this transaction status?

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

  What's next?

  • 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

• Show Hide

  83 - Refund refused

  How did I get this transaction status?

  • Oops! Your acquirer declined your refund request.

  What's next?

  • 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

• Show Hide

  84 - Payment declined by the acquirer

  How did I get this transaction status?

  • 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.

  What's next?

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

• Show Hide

  9 - Payment requested

  Congratulations! Your CreatePayment/CapturePayment request has been successful. The funds will be transferred to your account.

  How did I get this transaction status?

  • You have sent a CreatePayment/CreateHostedCheckout request for a new transaction with cardPaymentMethodSpecificInput.authorizationMode="SALE" which has been accepted by your acquirer
  • You have sent a CapturePayment request for an existing transaction with statusOutput.statusCode=5 or sent CreatePayment request with property cardPaymentMethodSpecificInput.authorizationMode="SALE" for a new transaction

  What's next?

  • You can refund the payment to your customer anytime. Please check our documentation how to do this in the Merchant Portal or sending a RefundPayment request
  • 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=8) or deleted (statusOutput.statusCode=7) respectively
• Show Hide

  91 - Payment processing

  How did I get this transaction status?

  • 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

  What's next?

  • 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)
• Show Hide

  92 - Payment uncertain

  How did I get this transaction status?

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

  What's next?

  • 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.
• Show Hide

  93 - Payment refused

  How did I get this transaction status?

  • Your acquirer declined your data capture request

  What's next?

  • 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.
• Show Hide

  99 - Being processed

  How did I get this transaction status?

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

  What's next?

  • 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.