Unico IDPay - DevCenter
HomepageAutenticaçãoAPI Reference
English
English
  • Introduction
  • ABOUT IDPAY
    • Unico ID Pay
    • Features
    • Use Cases
    • Chargeback
  • INTEGRATION
    • Overview
    • Authentication
      • Creating a Service Account
      • Preparing to make an authenticated request to the API
      • Additional resources
        • Example in JavaScript
        • Authentication Errors
        • Postman Collection
    • APIs
      • API Reference
        • Payment transactions
        • Chargeback
        • Credit card onboarding
      • Errors
      • Enumerated
    • Webhook
    • Controlling the experience
      • Overview
      • Requirements
      • Mobile
        • Android
        • Flutter
        • iOS
          • WKWebView
          • ASWebAuthenticationSession
      • Web
        • SDK
        • Redirect (deprecated)
    • Customizations
  • HELP & FAQ
    • FAQ
    • Best communication practices
    • Help Center
Powered by GitBook

Copyright © 2024 unico. All rights reserved.

On this page
  • Introduction
  • Possible Errors
  • Transaction Creation
  • Transaction status query
  • Recovery of the evidentiary set of the transaction
  • Resending the transaction notification
  • Credit card onboarding

Was this helpful?

Export as PDF
  1. INTEGRATION
  2. APIs

Errors

In this section, you will find an overview of the errors you may receive from the endpoints of the Unico IDPay product.


Introduction


Unico IDPay uses conventional HTTP response codes to indicate the success or failure of an API request.

As a general rule:

  • Codes in the 2xx range indicate success with the request.

  • Codes in the 4xx range indicate incorrect or incomplete parameters (for example, a mandatory parameter was omitted, or an operation failed with third parties, etc.).

  • Codes in the 5xx range indicate an error on the Unico IDPay product servers.

Unico IDPay also generates an error message and an error code formatted in JSON:

{
    "error": {
        "code": "40004",
        "description": "transaction id is invalid"
    }
}

Possible Errors


In this topic, you will find the possible errors for the endpoints, separated by their HTTP response.

Transaction Creation

HTTP Code
Code
Description
Reason

400

40001

error decoding json

The data sent does not match the service contract.

400

40002

error validating json

Some information is poorly formatted or missing.

400

40021

invalid phone

The provided phone number is invalid, it must follow the format: 55 DDD NUMBER. For example: 5543999999999.

400

40022

invalid email

The provided email is invalid.

400

40027

replicated transaction

The transaction sent already exists and cannot be created again.

400

40045

max value reached

When the transaction reaches a value higher than the allowed limit.

403

40301

not allowed

The user does not have permission to perform this action.

404

40404

company not found

The provided company does not exist.

429

40001

too many requests

Rate limit reached.

500

50001

internal error

Internal service failure.

Transaction status query


HTTP Code
Code
Description
Reason

400

40001

error decoding json

The data sent does not match the service contract.

400

40002

error validating json

Some information is poorly formatted or missing.

400

40004

transaction id is invalid

The transaction ID is invalid (format).

400

40301

not allowed

The user does not have permission to perform this action.

429

40401

transaction not found

The transaction was not found.

500

50001

internal error

Internal service failure.

Recovery of the evidentiary set of the transaction


HTTP Code
Código
Descrição
Motivo

400

40004

transaction id is invalid

The transaction ID is invalid (format).

400

40009

transaction status is invalid

The transaction status is invalid (not allowed for generating the proof set).

403

40301

not allowed

The user does not have permission to perform this action.

404

40401

transaction not found

The transaction was not found.

500

50001

internal error

Internal service failure.

Resending the transaction notification


HTTP Code
Código
Descrição
Motivo

400

40001

error decoding json

The data sent does not match the service contract.

400

40002

error validating json

Some information is incorrectly formatted or has not been filled out.

400

40004

transaction id is invalid

The transaction ID is invalid (format).

400

40009

transaction status is invalid

The transaction status does not allow notification resend (it is already completed).

400

40021

invalid phone

The phone number provided is invalid, it must follow the format: 55 DDD NUMBER. For example: 5543999999999.

400

40022

invalid email

The provided email is invalid.

403

40301

not allowed

The user does not have permission to perform this action.

404

40401

transaction not found

The transaction was not found.

429

40001

too many requests

Rate limit reached.

500

50001

internal error

Rate limit reached.

Credit card onboarding


HTTP Code
Código
Descrição
Motivo

400

40001

error decoding json

The data sent does not match the service contract.

400

40002

error validating json

Some information is either incorrectly formatted or missing.

400

40027

replicated transaction

The submitted transaction already exists and cannot be created again.

400

40030

invalid identity

The CPF provided in the request differs from the CPF associated with the specified processID.

400

40045

max value reached

When the transaction exceeds the permitted amount.

400

40054

processID is invalid

When the processID provided in the request is invalid (or does not exist).

400

40055

processID is expired

When the processID being used is too old.

403

40301

not allowed

The user does not have permission to perform this action.

404

40404

company not found

The specified company does not exist.

404

40410

processID not found

When the specified process does not exist.

404

40412

image not found

When the process specified by the user does not have an image.

429

40001

too many requests

Rate limit reached.

429

42901

too many requests

When the client is sending too many requests, exceeding the predefined limit.

500

50001

internal error

Internal service failure.


PreviousCredit card onboardingNextEnumerated

Last updated 1 month ago

Was this helpful?

Still need help?

Didn't find something or still need help? If you're already a client or partner, you can reach out through our .

​
Help Center