Share this page:
B2G errors

There are a range of errors that can occur when you are trying to transact on the PPSR using your B2G interface.

On this page

There are a range of errors that can occur when you are trying to transact on the PPSR using your B2G interface.

These are grouped into four main types:

  • Authentication errors (unable to authenticate the B2G user)
  • Validation errors (information unable to be validated against the register)
  • Unexpected errors (Error number 50001, server error, HTTP error without a valid PSPR message)
  • Transaction errors

For information on how your transaction errors will be charged, see transaction errors.

Basic processing flow for B2G transactions and where errors can occur

Basic processing flow for B2G transactions and where errors can occur

 

Authentication errors

‘Invalid user ID/password’, ‘account disabled’, ‘wrong IP address’ and ‘user locked’ are authentication errors.

Why errors occur

An authentication error will occur if the PPSR is unable to authenticate the B2G user trying to transact (e.g. invalid password provided). You must fix this error before attempting to transact again.

Validation errors

A validation error will occur if the information you provided in XML is unable to be validated against the PPSR (e.g. registration number and token do not match). If you receive a validation error, you need to fix the validation issue before trying to transact again.

Unexpected errors

‘Error number 50001’, ‘server error’, ‘HTTP error without a valid PPSR message’ are examples of unexpected errors.

Reason for error and response

There are a number of reasons for unexpected errors, including a:

  • code fault on the PPSR (retrying will get the same error)
  • badly formed request message (retrying will get the same error)
  • database load/contention (retrying may get a valid response)
  • network interruption (retrying may get a valid response)
  • time out in the network (retrying may get a valid response).

If you cannot resolve an errorlog an incident.

Transaction errors

The type of transaction you were performing and when the error occurred in the business process will determine if you will be charged.

Transaction charged to your account

If the error occurred after the business process was complete (e.g. registration or search request), the transaction will be charged to your account.

No charge

If you resend the identical request (with the same message ID), a standard response will be sent to you. This transaction will not result in a new charge to your account.

No refund

If you send the same request with a different message ID, your account will be charged. You will not be given a refund for this type of transaction.

Was this information helpful?

We welcome your feedback to help us improve our website.
Unfortunately we are unable to respond to individual comments or suggestions.

For enquiries please contact us