This guide provides a clear overview of two important transaction return codes—'Pending' and 'Successful, Flagged for Manual Review'—to ensure you handle both results correctly within your integration.

Result Code: 000.400.000 — Successful, Flagged for Manual Review

This code indicates that a payment was successful, but it has been flagged by a specific risk rule that you have configured on your account.

  • What it Means: This is a successful transaction, and the customer's card has been charged.

  • When It Occurs: This code is only sent if you have activated an optional, advanced risk check on your profile. For example, you might set up a rule to flag all transactions above a certain value. You will not receive this code with a standard account configuration, and these advanced checks may incur additional costs.

  • Required Action: This code is designed to be a signal to your system. You should use it to trigger an internal process, such as placing the order on hold and alerting your team to manually verify the transaction's legitimacy before shipping the goods or providing the service. It allows you to separate these pre-defined "high-risk" successes from standard successful transactions (000.000.000).

Result Code: 000.200.000 — Transaction Pending

This code represents a temporary, intermediate status in the transaction lifecycle. It is a normal and expected part of the API integration flow.

  • What it Means: This is a temporary status indicating that a checkout session has been created but has not yet been completed. The customer has not been charged at this stage.

  • When It Occours: This is a standard part of the Copy and Pay integration. It occurs at Step 1 when a checkoutID is generated, which happens before the customer is shown the payment form to enter their card details. Every card transaction will briefly be in this state.

  • Required Action: Your system should treat this as an intermediate step and wait for a final status update after the customer has submitted their payment details. Do not treat this as a success or failure.

Best Practice Recommendation: Implement Webhooks

To ensure you always receive the final, confirmed status of every transaction, we strongly recommend implementing webhooks.


While you can periodically poll our system for status updates (the 'get status call' in Step 3 of Copy and Pay), a network interruption could cause you to miss the final response from our server.


Webhooks provide a reliable, automated 'push' notification from our server directly to yours as soon as the final transaction status is known. This creates a crucial fail-safe for your order management system and prevents orders from getting stuck in a "pending" state.


More on available return codes