Order Statuses Requiring Manual Actions

To be able to recognize order statuses that require manual operations, refer to the table below. This table shows possible order statuses you may encounter. To learn how to process such orders, refer to Processing Stalled Orders.

Order Status

Description

Probable Cause

NP (No Payment Method Attached)

A customer does not have a document attached to an order, there is no associated payment method.

A customer does not have a default payment method.

WP (Waiting for Payment)

An order is to be consolidated with other customer's orders or the attached payment has not been processed yet. The required amount of money is not received yet, a service is not provisioned.

A customer has no credit card configured for automatic payments. A customer has paid in cash/check for the service.

WZ (Waiting for Payment after provisioning)

A service is provisioned while not all payments are received from a customer.

Some of the cases are:

  • If you configured a credit limit for a customer, service provisioning may be allowed before payment.

    For additional information on credit limits, please refer to Notes on Credit Limit.

  • If you have configured the Per Account billing type for a customer class, which means that you practically give your customers an unlimited credit line until a consolidated invoice is issued.

LO (Long Running Operation)

The system performs a certain time-consuming operation or waits for some action from an external system. The operation may fail in some cases eventually.

For example, a domain transfer operation.

PF (Provisioning Failed)

An order was paid, but there are some issues occurred at provisioning stage.

Some of the cases are:

  • Communication error with an external system has occurred.
  • There are not enough resources to provision a service.
  • There are no IP addresses available for allocation.
  • An order was marked as failed manually.

HL (Hold)

Normally means that a customer's order was put on hold, either automatically or manually.

SO was placed in the PCP for an account that is on hold.

SS (Suspected)

Fraud screening system recognized an order as potentially fraudulent.

For example, you have configured fraud screening rules that assign some points to a payment in the following cases:

  • On a first purchase, a customer may run out of attempts allowed to pay with the same credit card.
  • A customer's credit card is blacklisted.
  • A cardholder's email address is blacklisted.

If total score exceeds a Fraud Threshold, then an order gets status Suspected.

WA (Waiting for Approval)

If fraud screening is configured to set some order for manual check, the orders receive this status.

The WA status differs from SS as follows:

  • SS – an order marked as fraudulent by automatic check.
  • WA – an order has successfully passed fraud screening but requires a final check by a provider stuff member.

For example:

  • An order for $1,000 that is paid with the US credit card using an African IP address most probably will stuck in SS status.
  • An order for $1,000 that is paid with the US credit card by the US customer who successfully paid 10 previous orders is not suspicious, but a provider wants to review all orders with a large sum before processing.

MO (Manual Operation Required)

An order processing requires approval as an ordered service is provisioned by non-integrated external system.

For example, you are offering dedicated servers. The provisioning is manual, which means that when you have actually prepared and turned on the server, you can manually mark in Billing control panel that the service is ready.

TM (Manual Customer Account Verification is required)

A customer account should be activated by a provider for further service provisioning.

For example, the system was configured to require manual verification of customers from certain tax zones.

CloudBlue, an Ingram Micro business, uses cookies to improve the usability of our site. By continuing to use this site and/or logging in you are accepting the use of these cookies. For more information, visit our Privacy Policy.