Status and Result codes

Queued

Message is in a queue and has not been processed internally in our platform. Normally there should be very few messages with this status.

Sent

The message has been delivered to the recipient's operator, but we have not received any final status and do not know the final outcome. Status will change if and when we receive confirmation from the operator.

Failed

Message has not been delivered, see Detailed Status Code for more information.

Ok

Message has been delivered to end user's handset.

Delivered

Message has been delivered to end user's handset.

Expired

Message has been attempted to be delivered for more time than TimeToLive, default setting is 120 minutes. May be due to handset being off or outside service range.

Rejected

The message has not been delivered. The reason for the error can vary, but most often due to an invalid sender or recipient set on the message.

Stopped

Message is part of more than 100 identical messages within one hour and stopped, assuming it is part of an eternal loop. Stopped also applies if the message is sent to a restricted country code. Stopped also applies if the account has a set bulk cap per month, and this is exceeded.

MissingDeliveryReport

Operator has not given us final status.

OtherError

Message has not been delivered. This is an umbrella term for many different statuses. This is done so that you may avoid dealing with hundreds of different error-details. If you have a large number of messages with this status, please contact us so that we can analyze your traffic in more detail.

Undelivered

Message has not been delivered, unfortunately we have not received a more detailed delivery description.

UnknownSubscriber

Message not delivered, operator has no user of the number.

Created

The message has been created, but not yet sent to our internal queue.

Queued

The message has been queued in our internal system, and is awaiting processing.

Pending

The message has been sent to the RCS-operator.

Delivered

The message has arrived on the end user's handset, but not been read yet.

Displayed

The message has been delivered and read by the end user.

Failed

The message has not been successfully delivered. Reasons for this may include failed capability check, invalid message-content or problems at the operator.

Queued

Payment is in a queue internally in our platform and has not been delivered. Normally there should be very few with this status, but during big campaigns, the volume of these statuses can be significant for a time.

Sent

Payment request has been sent to Strex billing platform but has not been confirmed. We have not received any final status and do not know the final outcome. Status will change when we receive confirmation from Strex billing platform.

Failed

Payment has not been done, see Detailed Status Code for more information.

Ok

Payment has been done.

Reversed

Payment has been reversed.

Rebilled

Payment failed initially, but has been rebilled at a later point.

None

Payment has no status.

Delivered

Payment is delivered to destination.

Expired

The payment has not been completed and the "lifetime" of the message has expired. The billing has not been completed The TimeToLive of the billing has expired. Standard TimeToLive (time we try to charge) varies from method og action, some can be overwritten if you are technically integrated.

MissingDeliveryReport

Operator has not given us final status.

UnknownError

Obsolete. Replaced by OtherError.

Failed

Payment has not been completed, unfortunately we have not received a more detailed delivery description.

CardPSPError

The billing has not been completed. The end user has uploaded a bank card for debit, the debit has failed.

ConnectionOffline

The billing has not been completed, as it has not been possible to contact MNO.

Sent

Billing has not been confirmed, we have not received any final status and do not know the final outcome. Status may change if we receive confirmation from the operator.

Rejected

The billing has not been completed. The reason for the error can vary, but most often due to errors on the sender, errors on the recipient number or expired token.

UnknownSubscriber

The billing has not been completed. The reason is that the recipient's msisdn is not known.

SubscriberUnavailable

Subscriber unavailable.

SubscriberBarred

The billing has not been completed. The reason is that the recipient has blocked the possibility of debits via mobile payment, the recipient has to contact his operator and lift this block.

InsufficientFunds

The billing has not been completed. The reason is that the recipient does not have coverage on his prepaid card.

InvalidCredentials

The billling has not been completed, the transmission was made with the wrong username / password.

InvalidOTP

The billing has not been carried out, an invalid onetime password has been used.

MnoError

The billing has not been carried, due to an error at MNO.

RegistrationRequired

Billing requires that the user performs registration at Strex before the transaction can be completed.

UnknownAge

The billing has not been completed because the recipient's age is unknown. We do not know if the user is old enough in relation to the set age for the service.

DuplicateTransaction

The payment is not delivered. Same TransactionID is used before.

SubscriberLimitExceeded

The billing has not been completed. The reason is that the recipient has reached the limit for what can be charged per month. In some cases, there may also be an annual limit or a limit set at the user level.

MaxPinRetry

The billing has not been completed. Recipient has entered the wrong pin code too many times.

MissingPreAuth

The billing has not been completed. Process stopped since there is no valid active Token on MSISDN.

InvalidAmount

The billing has not been completed, because the amount is not valid. Either too high or too low.

OneTimePasswordExpired

The billing has not been completed. The one-time password sent to the recipient has expired the time limit.

OneTimePasswordFailed

The billing has not been completed. The reason is that the recipient has entered the wrong password.

Pending

The billing has not been completed. The reason is normally that we are waiting for an action from the end user, it can for example be registration or a confirmation via SMS or pin code.

SubscriberTooYoung

The billing has not been completed. The reason is that the recipient is younger than a set age limit for the service.

TimeoutError

The billing has not been completed. The reason is that the recipient has not performed the necessary action (eg registration or confirmation) within the set deadline.

Stopped

Message is part of more than 100 identical messages within one hour and stopped, assuming it is part of an eternal loop. Or the message is sent to a restricted country code.

UserInTransaction

The billing has not been completed and no notification has been delivered. The reason is that you have another assessment process active against the user.

Rebilled

Payment failed initially, but has been rebilled at a later point.

OtherError

Billing has not been completed. This is an umbrella term for many different statuses. This is done so that you may avoid dealing with hundreds of different error-details. If you have a large number of payments with this status, please contact us so that we can analyze your traffic in more detail.

Ok

The Vipps-transaction was successful.

Sent

Vipps has been asked to send a push to end user's app, awaiting callback with status.

Failed

The Vipps-transaction failed, see Detailed Status.

Reversed

The Vipps-transaction has been reversed, i.e. the money has been returned to the end user.

RESERVED

Payment reserved by user accepting the payment in Vipps.

CAPTURE

Sale OK.

CANCELLED

Payment cancelled by the user in Vipps.

REJECTED

User did not act on the payment (timeout, etc.).

INITIATE PAYMENT

Vipps has been asked to send a push to end user's app, awaiting callback with status.

INITIATE AGREEMENT

Asked Vipps to ask end user to accept recurring agreement.

CREATED AGREEMENT

The end user has accepted the recurring agreement.

CHARGED AGREEMENT

Recurring billing was successful.

EXPIRED AGREEMENT

The recurring agreement has been stopped by the end user.

PENDING AGREEMENT

Agreement has been created, but not approved by the user in the Vipps MobilePay app yet.

ACTIVE AGREEMENT

The agreement has been confirmed by the end user in the Vipps app and can receive charges.

STOPPED AGREEMENT

Agreement has been stopped, either by the merchant, or by the user by cancelling or rejecting the agreement.

User action required

Payment failed. Could be lack of funds, card is blocked for ecommerce, card is expired. If you want to send an email or similar to the user, you should encourage them to open the Vipps or MobilePay app and check the payment there to see why it is not paid. User will get notified in their Vipps or MobilePay app and need to take action. This could be to add funds to the card or change the card on the agreement.

Amount is higher than the users specified max amount

Amount is higher than the user's specified max amount. The user has a lower maxAmount on the variableAmount agreement than the amount of the charge. The user must update their maxAmount on the agreement for the charge to be processed.

Non technical error

Payment failed. Could be that the user has deleted their Vipps MobilePay profile. The user needs to take action in the app.

Technical error

Payment failed due to a technical error in Recurring or a downstream service. As long as the charge is not in the status FAILED, we are retrying the payment. If the status is FAILED and the customer has not been charged by any other means, we recommend creating a new charge with a new due date.