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
  • Transaction Result
  • Chargeback result

Was this helpful?

Export as PDF
  1. INTEGRATION
  2. APIs

Enumerated

In this section, you will find all the enumerations related to the Unico IDPay product.


Transaction Result


Code
Status type
Description

waiting

Intermediate

Waiting for information to be submitted

processing

Intermediate

In processing

shared

Intermediate

You have shared the capture, and we are waiting for the information to be submitted.

approved

Final

Approved

inconclusive

Final

We were unable to perform a conclusive validation.

expired

Final

Transaction expired

skiped

Final

The person skipped the biometric capture in the flow.

unknown-share

Final

The person marked that they do not recognize that purchase.

fast-inconclusive

Final

We were unable to perform a conclusive validation (pre-approval).

absent-holder

Final

When the cardholder is not present to complete the capture.

canceled

Final

When a transaction was manually canceled.

The development should account for scenarios where new statuses may appear, creating a rule. For example, if a status different from those mentioned in this article appears, follow a manual flow.

Chargeback result


Code
Status type
Description

waiting

Intermediate

Awaiting analysis

analyzing

Intermediate

In the process of analysis

approved

Final

Approved

refused

Final

Rejected

PreviousErrorsNextWebhook

Last updated 4 months 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