LogoLogo
  • OKP APIs
  • Getting Started with OKP
  • API Documentation
    • Deposits API
      • Technical and Security Aspects
        • Calculating the Signature
      • Endpoints
        • Deposit Creation Endpoint
          • Notifications
        • Transactional Account Endpoint
          • Understanding the Solution
        • PCI Deposit Creation Endpoint
        • Deposit Status Endpoint
        • Payment Methods Endpoint
        • Currency Exchange Endpoint
        • Crypto Exchange Endpoint
        • Country States Codes Endpoint
        • Refund Creation Endpoint
          • Notifications
        • Refund Status Endpoint
      • Payment Methods
        • ๐ŸŒŽAmerica
          • ๐Ÿ‡ง๐Ÿ‡ทBrazil
            • PIX Biometric
      • API Codes
    • Cashouts API
      • Technical and Security Aspects
        • Calculating the Payload-Signature
      • Endpoints
        • Cashout Creation Endpoint
          • Notifications
        • Cashout Status Endpoint
        • Cashout Update Status Endpoint
        • Cashout Cancellation Endpoint
        • Cashout Bank Codes
      • Countries Validations
        • American Countries
          • ๐Ÿ‡ง๐Ÿ‡ทBrazil
      • API Codes
    • Subscriptions API
      • Technical and Security Aspects
        • Calculating the Signature
      • Subscription Creation Endpoints
        • OneShot Subscription Creation
        • PCI Subscription Creation Endpoint
        • Notifications
      • Subscription Cancellation Endpoint
      • Subscription Status Endpoint
    • Quickpay
      • Endpoints
        • Deposit creation endpoint
          • Notifications
        • Deposit status endpoint
    • Bank Account Validation
      • Technical and Security Aspects
        • Calculating the Signature
      • Endpoints
        • Bank Account Validation Endpoint
          • Pix Key Validation and Details Endpoint
      • API Codes
    • KYC API
      • Technical and Security Aspects
        • Calculating the Signature
      • KYC Endpoint
      • API Codes
  • Deposits Tools
    • Cards SDK
      • With User Interface
        • ๐Ÿš€Color Customization
      • Without User Interface
    • Java SDK
    • PHP SDK
  • Knowledge Base
    • Deposits with Cards SDK
      • With User Interface
      • Without User Interface
    • Countries Specifications
  • PLUGINS
    • WooCommerce
      • Installation
      • Configuration
  • Status Page
Powered by GitBook
On this page
  1. API Documentation
  2. Bank Account Validation
  3. Endpoints
  4. Bank Account Validation Endpoint

Pix Key Validation and Details Endpoint

Validate PIX Keys in real time, with their full banking details.

Account Validation Request

POST https://api-stg.onekeypayments.com/v5/account/pix_key/validate/details

This endpoint allows you to validate if a Pix Key exists, and what banking details are tied to this PIX key

Check with your Account Manager or Technical Account Manager regarding the production API endpoint.

Headers

Name
Type
Description

Content-Type*

string

application/json

X-Date*

string

ISO8601 Datetime with Timezone: yyyy-MM-dd'T'HH:mm:ssZ

X-Login*

string

Merchant X-Login Cashouts API Key

Authorization*

string

Authorization control hash

Request Body

Name
Type
Description

key_type*

String

Type of the PIX, this can be either DOCUMENT, EMAIL , PHONE or RANDOM_ID

document*

String

CPF of the customer.

pix_key*

String

Contains the value of the PIX key that you want to get the details for.

notification_url*

String

API URL utilized to receive the banking information from your side.

Example Request

{
"key_type": "DOCUMENT",
"document": "29318456719",
"pix_key": "29318456719",
"notification_url": "https://test.com"
}

Response

{
"document": "29318456719",
"pix_key": "29318456719",
"message": "The Pix validation is in progress",
"status": "IN_PROGRESS"
}
{
"document" : "29318456719",
"pix_key" : "29318456719",
"status" : "ERROR",
"message" : "The Pix key is not valid."
}

Callback After obtaining the HTTP 200 response, we'll send a callback to your previously designated notification_url, this will include all the following banking information, tied to the Pix key:

{
"key_type": "DOCUMENT",
"pix_key": "29318456719",
"bank_account": 1234567,
"bank_branch": 0199,
"bank_code": 33,
"ispb_code": 90400888,
"account_type": "SAVINGS",
"is_licensed": true | false
}

In this case, the PIX KEY DOCUMENT "29318456719" would be tied to the banking details in the response.

Error callback This happens for example when the account CPF does not match the one sent

{
    "document": "96247806175",
    "pix_key": "96247806175",
    "message": "An error ocurred during the validation",
    "status": "ERROR"
}

API Messages

status

Message

Description

IN_PROGRESS

The Pix validation is in progress

The PIX Key exists and we are validating the bank account details

ERROR

The Pix key does not belong to the document

The account associated to PIX Key sent does not belong to the document sent in the request.

ERROR

The document is not a CPF

The CPF provided is invalid.

ERROR

The Pix Key is invalid

The PIX Key does not exist or itโ€™s greylisted.

PreviousBank Account Validation EndpointNextAPI Codes

Last updated 4 months ago