{"activeVersionTag":"latest","latestAvailableVersionTag":"latest","collection":{"info":{"_postman_id":"4fcb2690-a0f4-444e-8100-8007cd8e55af","name":"API Connect PSP","description":"### With the ConnectPSP API, you will have access to a robust and flexible system designed to manage the essential financial operations of your business, including Cash-in, Cash-out, balance control, and integrations via Webhook.\n\n### _**To simplify complex financial processes, enabling businesses to focus on growth.**_\n\n# **Table of Contents**\n\n1. Overview\n \n2. **Regulatory Compliance**\n \n3. KYC (Know Your Customer)\n \n4. Initial Setup\n \n 1. Environment and Authorization\n \n 2. Allowed IP List to Connect PSP\n \n 3. Access to Connect PSP Homologation Environment\n \n5. API Request\n \n6. Authentication Flow\n \n7. Available Endpoints\n \n 1. [Token](https://go.postman.co/workspace/f9d4164d-3eb0-4dca-8c10-251723a91eeb/documentation/40974951-4fcb2690-a0f4-444e-8100-8007cd8e55af?entity=request-a1b427db-ea29-4760-9efe-49256c61cc1a)\n \n 2. [Deposit (PaymentPix)](https://go.postman.co/workspace/f9d4164d-3eb0-4dca-8c10-251723a91eeb/documentation/40974951-4fcb2690-a0f4-444e-8100-8007cd8e55af?entity=request-6325f11b-3229-4b9f-86fb-389489dd186e)\n \n 3. [Withdrawal (TransferPix)](https://go.postman.co/workspace/f9d4164d-3eb0-4dca-8c10-251723a91eeb/documentation/40974951-4fcb2690-a0f4-444e-8100-8007cd8e55af?entity=request-127fd0dd-68d0-4e5f-9f28-9f46814defda)\n \n 4. [Move Balance Between Transactional and Proprietary Accounts (Rebalance)](https://go.postman.co/workspace/f9d4164d-3eb0-4dca-8c10-251723a91eeb/documentation/40974951-4fcb2690-a0f4-444e-8100-8007cd8e55af?entity=request-3adfebf6-3ef7-4018-9e20-68b13aaa4a72)\n \n 5. [Balance Inquiry (GetRealBalance)](https://go.postman.co/workspace/f9d4164d-3eb0-4dca-8c10-251723a91eeb/documentation/40974951-4fcb2690-a0f4-444e-8100-8007cd8e55af?entity=request-79881d69-a122-4230-a930-b49b96694aa9)\n \n 6. [Balance by Date Inquiry (GetRealBalanceByDate)](https://go.postman.co/workspace/f9d4164d-3eb0-4dca-8c10-251723a91eeb/documentation/40974951-4fcb2690-a0f4-444e-8100-8007cd8e55af?entity=request-749e5835-7694-4d7a-b118-04fa29611414)\n \n 7. [Account Balance Inquiry (GetRealBalanceSummary)](https://go.postman.co/workspace/f9d4164d-3eb0-4dca-8c10-251723a91eeb/documentation/40974951-4fcb2690-a0f4-444e-8100-8007cd8e55af?entity=request-136e21d1-e0f3-4812-8c98-98b958f7432a)\n \n\n# Overwiew\n\n## **Core Operations**:\n\n1. **Cash-In**: Efficient and reliable payment collection using personalized QR codes and real-time payment confirmations.\n \n2. **Cash-Out**: Fast and secure withdrawal processes with real-time updates.\n \n3. **Balance Management**: Tools for balance inquiries and internal fund transfers.\n \n4. **Webhook Integration**: Real-time monitoring of deposits and withdrawals.\n \n\n## **Key Features**\n\n• **Speed and Security**: All transactions are fast, traceable, and compliant with financial regulations.\n\n• **Modern Integration**: API provides a seamless and robust system for financial operations.\n\n• **Regulatory Compliance**: Strict adherence to national financial regulations ensures secure and transparent operations.\n\n## **Cash-In Operations**\n\n- **Capabilities**:\n \n\n1. Generate personalized QR codes for immediate use.\n \n2. Receive automatic payment confirmations for better control.\n \n3. Enhances customer experience.\n \n4. Ensures reliable and efficient payment processes.\n \n5. Integration with OpenFinance for direct payments with biometric confirmation.\n \n\n## _**Cash-Out Operations**_\n\nConnectPSP API integrates a robust suite of quarantine and security controls to ensure all withdrawal operations are secure, compliant, and tailored to business needs. These measures provide multi-layered protection while maintaining operational efficiency.\n\n**Third-Party Blocking**: Prevents unauthorized withdrawals to third-party accounts, ensuring funds are transferred only to designated recipients.\n\n**Time-Based Quarantine**: Enforces a one-minute quarantine for transactions outside the 20-second operational window, mitigating risks of suspicious activities.\n\n## **Blacklist Enforcement**:\n\n- Blocks transactions involving flagged ISPB codes, CPF numbers, or PIX keys.\n \n- Protects against high-risk or fraudulent entities.\n \n\n## **Third-Party Withdrawal Control**:\n\nAdds an additional verification layer for withdrawals directed to non-primary accounts.\n\n## Withdrawal limit controls:\n\n- **Transaction Limits**: Controls the maximum withdrawal amount per transaction.\n \n- **Night/Day Limits**: Sets specific withdrawal caps for nighttime and daytime periods, reducing off-peak vulnerabilities.\n \n- **Daily Limits**: Establishes a maximum withdrawal threshold per day for added oversight.\n \n- **Quantity Limits**: Restricts the number of withdrawals allowed during the day to prevent abuse.\n \n- **Beneficiary-Specific Limits**: Caps the withdrawal amount or frequency for specific recipients.\n \n- **Client-Specific Limits**: Customizes withdrawal restrictions for individual clients based on their profiles and risk assessments.\n \n- **Double-Check Limits**: Requires additional verification for withdrawals exceeding predefined thresholds, ensuring high-value transactions are legitimate.\n \n\n## **Webhooks**\n\nConnectPSP API introduces a dynamic webhook feature, allowing you to define the notification endpoint for each transaction. This approach provides unmatched flexibility, empowering businesses to manage real-time notifications with precision and adaptability.\n\n- **Transaction-Specific Webhooks**: Assign unique webhook URLs per operation, ensuring tailored notifications for each workflow.\n \n- **Seamless Integration**: Easily adapt webhook endpoints to different systems or use cases without modifying centralized configurations.\n \n- **Improved Security**: Webhook usage is scoped to specific transactions, reducing exposure and enhancing operational safety.\n \n- **Real-Time Monitoring**: Temporary webhook endpoints can be used for debugging or validation, providing immediate feedback during development and testing.\n \n- **Operational Resilience**: Dynamic webhooks enable quick adjustments, ensuring uninterrupted notifications even during endpoint changes or failures.\n \n\n---\n\n# Regulatory Compliance\n\nConnectPSP is fully committed to security and transparency. Our API strictly adheres to the national financial regulations, including:\n\n- Rigorous management of proprietary and transactional accounts.\n \n- Dedicated endpoints for balance inquiry and transfer.\n \n\n**We have simplified the integration process with our clients and partners, here is a brief summary of the main features for the regulated market.**\n\n## **Rebalancing**\n\nAdjusts account balances by debiting or crediting between transactional or proprietary accounts. Simplify your operations in the critical process of reconciling the balances between the graphical accounts of your clients and the monetary value of their transactional accounts.\n\n_**The rebalancing process for the regulated market is available in two ways.**_\n\n### **Semi-automatic**\n\nFirstly, we are activated and receive information about the total amount that represents the balance of the users in the graphic accounts, after which the whole process takes place automatically, ensuring that it complies with the requirements of the regulations.\n\n\n\n### **Automatic**\n\nWe automatically contact your partner to obtain the balance information and distribute the values through intelligent and totally reliable processes, offering security, reliability, integrity and reducing human error.\n\n\n\n> **Important:** Depending on the partner, it may be necessary to make adjustments so that the balance of the graphic accounts can be obtained; this process requires two working days of development. \n \n\n## **Real Balance**\n\nReturns the current transactional account balance, allowing quick and easy retrieval.\n\n## **Real Balance By Date**\n\nLets you see the opening and closing balance of transaction and own accounts for a given date (in YYYY-MM-DD BRT format).\n\n## **Real Balance Summary**\n\nReturns a complete summary of the current balance of the transactional and proprietary accounts.\n\nBy choosing the ConnectPSP API, you’re opting for a solution that not only meets the demands of the regulated market but also protects your resources and business in a robust and reliable way.\n\n## **Security and Compliance**\n\nThe ConnectPSP API incorporates advanced security features designed to safeguard withdrawal operations. These measures ensure the API is resilient against threats while providing users with secure, reliable, and compliant transactions.\n\n- **Fraud Prevention**: Detects and blocks potentially fraudulent transactions in real time.\n \n- **Compliance Assurance**: Adheres to regulatory requirements by applying stringent controls to high-risk scenarios.\n \n- **Operational Control**: Enables precise customization of limits to align with business policies and customer profiles.\n \n- **Minimized Risk Exposure**: Reduces vulnerabilities during off-peak hours or when dealing with high-value transactions.\n \n- **Enhanced Traceability**: Provides detailed tracking and reporting for all withdrawal operations, supporting audits and investigations.\n \n\n---\n\n# KYC (Know Your Customer)\n\nConnectPSP is committed to providing secure and reliable solutions for its clients. As part of this commitment, we have implemented the **Know Your Customer (KYC)** process in our API. This process aims to verify the identity of end users on betting platforms that use our services, ensuring compliance with current regulations and enhancing transaction security.\n\n## What is the KYC Process?\n\nKYC is a procedure used to confirm users' identities, preventing fraud, money laundering and ensuring that activities comply with applicable laws and regulations. At ConnectPSP, the KYC process involves verifying the data provided by users through:\n\n- **Facial Capture**: Comparing the user's facial image with the photo in their identification document.\n \n- **Document Analysis**: Verifying the authenticity of the submitted documents.\n \n\n## Benefits of the KYC Process\n\nImplementing KYC in the ConnectPSP API offers several benefits:\n\n- **Enhanced Security**: Reduces risks of fraud and illicit activities.\n \n- **Regulatory Compliance**: Ensures adherence to financial sector legal and regulatory requirements.\n \n- **Money laundering prevention:** Helps identify and prevent money laundering activities, ensuring a more transparent and secure financial environment.\n \n- **User Trust**: Increases credibility with end users, making them feel safer when using the platform.\n \n- **Efficient Management**: Improves risk management and enables informed decision-making.\n \n\n## How the KYC Process Works in the ConnectPSP API\n\nOur API is designed to simplify the integration of the KYC process into our clients' platforms. Below are the key steps involved:\n\n1. **Session Initiation**: The client starts a verification session through the API, preparing the environment for user data collection.\n \n2. **Data Collection**: The necessary user data is collected, including personal information, identification documents, and facial capture.\n \n3. **Data Verification**: The API verifies the provided data by comparing the facial capture with the document photo and validating the authenticity of the information.\n \n4. **Results Return**: After verification, the API automatically sends a callback to the client's configured endpoint. This callback provides a detailed analysis of the collected data, allowing the client to assess and decide whether to approve the user or take additional actions, ensuring complete control over the process.\n \n\n## Technical Implementation\n\nTo integrate the KYC process into your platform using the ConnectPSP API, follow these steps:\n\n1. **Authentication and Authorization**: The authentication and authorization process follows the same pattern used in the other endpoints of our API. For more details, refer to **API Request Index > HTTP Request Headers**.\n \n2. **Session Initiation**: Call the `OpenSession` to start a new verification session.\n \n3. **Data Submission**: Send the collected user data, including documents and facial capture, to the API.\n \n4. **Return Callback:** After processing the data, the API automatically sends a callback to the client’s configured endpoint, providing detailed analysis and verification results for informed decision-making.\n \n\n# **Available KYC Processes**\n\n## **Onboarding**\n\n**Onboarding** is the starting point of the **Know Your Customer (KYC)** process, ensuring user identity verification through different flows. This process is structured into three modalities:\n\n| Flow | Purpose |\n| --- | --- |\n| DOCUMENTOSCOPY | Captures the user's identity document.
Ensures the image quality of the captured document.
Automatically extracts the relevant information from the document. |\n| LIVENESS | Performs biometric capture of the user.
Conducts liveness detection to validate biometric authenticity. |\n| ONBOARDING | Captures facial biometrics with liveness detection.
Captures the identity document and ensures image quality.
Performs face matching between the captured biometrics and the document photo. |\n\n## **Process Flow**\n\n- **Session Initialization:**\n \n - The client sends a **request to the OpenSession API** with the necessary data.\n \n - In response, the API returns an **iFrame URL**, which will be used for the capture process.\n \n- **Data Capture:**\n \n - The URL renders a **QR Code** for the user to scan.\n \n - The QR Code redirects the user to **facial biometric and/or document capture**, depending on the **validationType** specified in the request.\n \n- **URL Validity:**\n \n - The onboarding URL has an expiration time of approximately 10 minutes.\n \n - If the time expires before completion, a **Page Expired** message will be displayed, requiring the user to restart the process.\n \n- **Redirection:**\n \n - The client can configure a **callback URL** to redirect the user after completing the onboarding process.\n \n - Example: [https://kyc.connectpsp.com/onboarding/f64ba65e-8599-4b83-91e5-9cdf28a79ea6](https://kyc.connectpsp.com/connectpsp/onboarding/f64ba65e-8599-4b83-91e5-9cdf28a79ea6)[?callback=https://connectpsp.com](https://kyc.connectpsp.com/onboarding?callback=https://connectpsp.com)\n \n- **Result Return:**\n \n - After the capture is completed, the API sends a **callback** to the client with the analysis results of the submitted and captured data.\n \n\nThis process ensures that user identities are verified with **security, efficiency, and regulatory compliance**, providing a seamless integration with the **ConnectPSP** API.\n\n## **Basic Registration Data**\n\nThe **Basic Registration Data** dataset provides fundamental identity information retrieved from official sources, combined with inferred and related data. Examples of returned information include **full name, CPF (tax ID), mother's name, and date of birth**.\n\nThis dataset aggregates data from various sources, including the **Brazilian Federal Revenue (and equivalent agencies abroad), the National Social Information Registry (CNIS), judicial records, and numerous other specific databases**. Additionally, death records are obtained from the Brazilian Federal Revenue and professional associations.\n\n## **KYC and Compliance**\n\nThe **KYC and Compliance** dataset provides information essential for meeting **regulatory and legal requirements** related to identity verification. It includes data on **politically exposed persons (PEPs), sanctions, and restrictions**, both nationally and internationally.\n\nAlongside flags indicating whether an individual is classified as a PEP or has any associated restrictions, the dataset also includes **historical records**. If a person was a PEP in the past, the current flag will not be set, but their historical status will be available for analysis.\n\nBeyond traditional PEP classifications, we also offer an **Extended PEP concept**, identifying individuals related to a PEP through **distant family connections or other types of relationships**. The dataset specifies the nature of these relationships. For example, if the dataset returns `\"mother\" (MOTHER)`, it means the individual is the mother of someone classified as a PEP.\n\nAll information in this dataset originates from **official national and international institutions**, such as **OFAC, INTERPOL, the Brazilian Federal Court of Accounts, the National Justice Council**, and many others.\n\n## **Social Assistance and Benefit Programs**\n\nThe **Social Assistance and Benefit Programs** dataset provides insights into **government-issued social benefits** received by individuals. This allows for the identification of people enrolled in programs such as **Bolsa Família, unemployment insurance for fishermen (Seguro Defeso), emergency aid (COVID-19 relief), and similar initiatives**.\n\nIn addition to a summary of received benefits, this dataset offers **detailed records of each identified benefit**, even those no longer active, enabling a historical view of assistance received over time.\n\nData associations rely on **name, date of birth, and residence information**, which may result in missing records when an exact **one-to-one** match is not possible.\n\nAll data is sourced from **publicly available government records**, including **transparency portals and centralized information systems**.\n\n## **Sports Exposure**\n\nThe **Sports Exposure** dataset identifies individuals with **direct or indirect ties to sports organizations**. When available, it also includes **professional history details and specific information about the associated sports entity**. One key application of this dataset is to ensure compliance with **Law 14.790 (KYC for sports betting)**.\n\nData sources include **public records from sports-related entities**, such as the **Brazilian Football Confederation (CBF) and official club websites**. While primarily focused on football, the dataset also includes information from other sports disciplines, including **futsal, handball, volleyball, basketball, tennis, athletics, and gymnastics**.\n\n---\n\n# **Initial Setup**\n\n## Environment and Authorization\n\n- All calls are made via HTTPS.\n \n- Authentication is performed through the [Token](https://www.postman.com/connect-psp/connect-psp/request/m4v5glu/token?action=share&source=copy-link&creator=40974951&ctx=documentation) endpoint.\n \n- Provide your IP to be whitelisted in the production environment. For the homologation environment, this is not required.\n \n\n## Environments:\n\n| **Type** | **URL** | Outbound IPs |\n| --- | --- | --- |\n| Production | [https://api.connectpsp.com](https://api.connectpsp.com) | 44.198.78.149 / 3.140.64.215 / 13.58.52.247 / 56.126.107.142 |\n| Homologation | [https://api.homologacao.connectpsp.com](https://api.homologacao.connectpsp.com) | 3.223.125.52 / 52.22.174.73 |\n\n> **When integrating the IP, an e-mail must be sent requesting the release of the IP to the address** [itsec@connectpsp.com](https://mailto:itsec@connectpsp.com)**.** \n \n\n## Access to Connect PSP Homologation Environment\n\nTo integrate your system with Connect PSP's Homologation environment and simulate operations as if you were in the production environment, you will need specific credentials for authentication and API usage.\n\n> **To speed up the process, you can request the credentials from the sales team and** send an email to [integracoes@connectpsp.com](https://mailto:integracoes@connectpsp.com) requesting access credentials for the homologation environment. \n \n\n\"Process%20for%20requesting%20credentials%20in%20homologation\"\n\n**Pass on the company's basic information such as CNPJ, your access will be validated and authorized internally, it will contain a value of R$ 2.00 reais for the homologation scope.**\n\nOnce we receive your request, our team will validate it and reply via email with the necessary credentials. With these credentials, you will be able to generate an authentication Token and start using the API endpoints.\n\nWe’re here to assist you at every step of the integration process. If you have any questions, feel free to reach out!\n\n---\n\n# **API Request**\n\nTo make an API request, combine the HTTP method (**GET**, **POST**, or **PUT**), the API service URL, the URI for a resource to be queried, sent data, or updated, and one or more HTTP request headers.\n\n## API Service URLs:\n\n- **Production**: [https://api.connectpsp.com](https://api.connectpsp.com)\n \n- **Homologation**: [https://api.homologacao.connectpsp.com](https://api.homologacao.connectpsp.com)\n \n\n## HTTP Request Headers\n\nThe following are the most commonly used HTTP request headers:\n\n### Content-Type\n\nSpecifies the format of the request, required for operations with a request body. The syntax is: `Content-Type: application/format` \nFor the `token` endpoint the `format` receives `x-www-form-urlencoded` \nFor other endpoints the `format` gets `json`\n\n### ApplicationToken\n\nThis is a security key automatically generated when you register your application in the ConnectPSP dashboard.\n\nIf you already have a registered application and don’t remember the value, you can retrieve it by accessing your dashboard and navigating to:\n\n- **Integrations > Applications**\n \n- The screen will display the ApplicationToken of the registered application.\n \n\n### Authorization\n\nThis header is mandatory for almost all requests. Its value is composed of `{{vault:bearer-token}}`. \nThe value of `access_token` is obtained in the response from the **Token** endpoint.\n\n### DigitalSignature\n\nA required key for account balance-related queries and payment requests. \nFor payments, the value is provided in the request body. \nTo generate the `digitalSignature`, follow these steps:\n\n- _**Get the Acces_Token**_ \n Get the value of the `access_token` in the response of the request from the _token_ endpoint. \n The token will be returned in the response body, as in the example below:\n \n\n``` json\n{\n \"access_token\": \"\",\n \"token_type\": \"bearer\",\n \"expires_in\": 3599\n}\n\n ```\n\n- **Generate HMAC-SHA256** \n Whith the `access_token` in hand, use the [HMAC-SHA256 ](https://www.devglan.com/online-tools/hmac-sha256-online) function. It requires two input parameters:\n \n - The `access_token` you have just obtained.\n \n - The Security Token that you generate in In ConnectPSP in Integrations.\n \n\nThe result of this operation must be stored in a variable. \n_**Example**_\n\n``` javascript\nvar signBytes = CryptoJS.HmacSHA256(res.json().access_token, pm.collectionVariables.get('CRP-TOKEN'));\n\n ```\n\n- **Converts to a hexadecimal string** \n _The next step is to transform the result of_ **HMAC-SHA256** into a hexadecimal string, using an appropriate function. The string generated will be stored in another variable called **signHex**.\n \n\n**Exemplo**\n\n``` javascript\nvar signHex = CryptoJS.enc.Hex.stringify(signBytes);\n\n ```\n\n- **Use digitalSignature** \n _The hexadecimal string stored in the_ **signHex** variable will be used in the request body, in the `“digitalSignature”` property.\n \n\n### **x-request-id**\n\nThe x-request-id parameter is optional, but can be used to insert a hash code at the time of withdrawal. Below are the details on how to use it:\n\n- **x-request-id format**\n \n - The value must be sent **in capital letters**.\n \n - This field accepts values of up to **68 characters**.\n \n- **Encryption of the value**\n \n - The value entered in **x-request-id** will be encrypted using **Applicationtoken** as the key.\n \n - The encryption will be carried out using the **HMAC-SHA256** method, which uses two parameters:\n \n - The first is the value of the **x-request-id**.\n \n - The second is the value of the **Applicationtoken**.\n \n - Practical example \n You can use online tools such as [Devglan HMAC-SHA256](https://www.devglan.com/online-tools/hmac-sha256-online) to encrypt the token.\n \n- **Use of x-request-id** \n The parameter will be used in the callback control for successful operations, allowing greater traceability.\n \n\n---\n\n# Authentication Flow\n\n1. Obtain a token using the `/api/v1/token` endpoint.\n \n2. Use the token in the `Authorization` header to access other endpoints.\n \n3. Remember to renew the token when it expires (after 1 hour).","schema":"https://schema.getpostman.com/json/collection/v2.0.0/collection.json","isPublicCollection":true,"owner":"40974951","collectionId":"4fcb2690-a0f4-444e-8100-8007cd8e55af","publishedId":"2sAYQXpYm6","public":true,"publicUrl":"https://doc.connectpsp.com","privateUrl":"https://go.postman.co/documentation/40974951-4fcb2690-a0f4-444e-8100-8007cd8e55af","customColor":{"top-bar":"c2a1cd","right-sidebar":"333333","highlight":"4B0082"},"documentationLayout":"classic-double-column","customisation":{"metaTags":[{"name":"description","value":"Simplify secure financial operations with ConnectPSP API. Robust controls for withdrawals, deposits, and real-time monit"},{"name":"title","value":"ConnectPSP"}],"appearance":{"default":"light","themes":[{"name":"dark","logo":"https://content.pstmn.io/5ce70294-43f2-46bb-8cc0-9d558de32712/Y3JvcHBlZC00YjAwODItMi0yNjd4NjUgKDEpLnBuZw==","colors":{"top-bar":"FFFFFF","right-sidebar":"333333","highlight":"9a6dfd"}},{"name":"light","logo":"https://content.pstmn.io/be7a4daf-54fb-4f37-8828-efa70358fbe6/Y3JvcHBlZC00YjAwODItMi0yNjd4NjUgKDEpLnBuZw==","colors":{"top-bar":"c2a1cd","right-sidebar":"333333","highlight":"4B0082"}}]}},"version":"8.11.11","publishDate":"2025-01-15T04:37:41.000Z","activeVersionTag":"latest","documentationTheme":"light","metaTags":{"title":"ConnectPSP","description":"Simplify secure financial operations with ConnectPSP API. Robust controls for withdrawals, deposits, and real-time monit"},"logos":{"logoLight":"https://content.pstmn.io/be7a4daf-54fb-4f37-8828-efa70358fbe6/Y3JvcHBlZC00YjAwODItMi0yNjd4NjUgKDEpLnBuZw==","logoDark":"https://content.pstmn.io/5ce70294-43f2-46bb-8cc0-9d558de32712/Y3JvcHBlZC00YjAwODItMi0yNjd4NjUgKDEpLnBuZw=="}},"statusCode":200},"environments":[{"name":"Homologation","id":"bcb9599d-eda7-4b0e-a345-c127afbe3b9f","owner":"40974800","values":[{"key":"URI_BASE","value":"https://api.homologacao.connectpsp.com","enabled":true,"type":"default"},{"key":"PXB-USERNAME","value":"To access the homologation environment, please request access via email at integracoes@connectpsp.com","enabled":true,"type":"default"},{"key":"PXB-PWD","value":"To access the homologation environment, please request access via email at integracoes@connectpsp.com","enabled":true,"type":"default"},{"key":"PXB-TOKEN","value":"To access the homologation environment, please request access via email at integracoes@connectpsp.com","enabled":true,"type":"default"},{"key":"PXB-CRP-TOKEN","value":"To access the homologation environment, please request access via email at integracoes@connectpsp.com","enabled":true,"type":"default"},{"key":"ASSINATURADIGITAL","value":"","enabled":true,"type":"default"},{"key":"ACCESSTOKEN","value":"","enabled":true,"type":"secret"},{"key":"WEBHOOK","value":"https://webhook.site/#!/view/c0dbeea2-ae8b-412a-8910-2932a061d4e9","enabled":true,"type":"default"}],"published":true}],"user":{"authenticated":false,"permissions":{"publish":false}},"run":{"button":{"js":"https://run.pstmn.io/button.js","css":"https://run.pstmn.io/button.css"}},"web":"https://www.getpostman.com/","team":{"logo":"https://res.cloudinary.com/postman/image/upload/t_team_logo_pubdoc/v1/team/c2acb420788e65a5ae1766173ae44b075d922faa385deea32b403488a2d0a892","favicon":"https://connectpsp.com/favicon.ico"},"isEnvFetchError":false,"languages":"[{\"key\":\"csharp\",\"label\":\"C#\",\"variant\":\"HttpClient\"},{\"key\":\"csharp\",\"label\":\"C#\",\"variant\":\"RestSharp\"},{\"key\":\"curl\",\"label\":\"cURL\",\"variant\":\"cURL\"},{\"key\":\"dart\",\"label\":\"Dart\",\"variant\":\"http\"},{\"key\":\"go\",\"label\":\"Go\",\"variant\":\"Native\"},{\"key\":\"http\",\"label\":\"HTTP\",\"variant\":\"HTTP\"},{\"key\":\"java\",\"label\":\"Java\",\"variant\":\"OkHttp\"},{\"key\":\"java\",\"label\":\"Java\",\"variant\":\"Unirest\"},{\"key\":\"javascript\",\"label\":\"JavaScript\",\"variant\":\"Fetch\"},{\"key\":\"javascript\",\"label\":\"JavaScript\",\"variant\":\"jQuery\"},{\"key\":\"javascript\",\"label\":\"JavaScript\",\"variant\":\"XHR\"},{\"key\":\"c\",\"label\":\"C\",\"variant\":\"libcurl\"},{\"key\":\"nodejs\",\"label\":\"NodeJs\",\"variant\":\"Axios\"},{\"key\":\"nodejs\",\"label\":\"NodeJs\",\"variant\":\"Native\"},{\"key\":\"nodejs\",\"label\":\"NodeJs\",\"variant\":\"Request\"},{\"key\":\"nodejs\",\"label\":\"NodeJs\",\"variant\":\"Unirest\"},{\"key\":\"objective-c\",\"label\":\"Objective-C\",\"variant\":\"NSURLSession\"},{\"key\":\"ocaml\",\"label\":\"OCaml\",\"variant\":\"Cohttp\"},{\"key\":\"php\",\"label\":\"PHP\",\"variant\":\"cURL\"},{\"key\":\"php\",\"label\":\"PHP\",\"variant\":\"Guzzle\"},{\"key\":\"php\",\"label\":\"PHP\",\"variant\":\"HTTP_Request2\"},{\"key\":\"php\",\"label\":\"PHP\",\"variant\":\"pecl_http\"},{\"key\":\"powershell\",\"label\":\"PowerShell\",\"variant\":\"RestMethod\"},{\"key\":\"python\",\"label\":\"Python\",\"variant\":\"http.client\"},{\"key\":\"python\",\"label\":\"Python\",\"variant\":\"Requests\"},{\"key\":\"r\",\"label\":\"R\",\"variant\":\"httr\"},{\"key\":\"r\",\"label\":\"R\",\"variant\":\"RCurl\"},{\"key\":\"ruby\",\"label\":\"Ruby\",\"variant\":\"Net::HTTP\"},{\"key\":\"shell\",\"label\":\"Shell\",\"variant\":\"Httpie\"},{\"key\":\"shell\",\"label\":\"Shell\",\"variant\":\"wget\"},{\"key\":\"swift\",\"label\":\"Swift\",\"variant\":\"URLSession\"}]","languageSettings":[{"key":"csharp","label":"C#","variant":"HttpClient"},{"key":"csharp","label":"C#","variant":"RestSharp"},{"key":"curl","label":"cURL","variant":"cURL"},{"key":"dart","label":"Dart","variant":"http"},{"key":"go","label":"Go","variant":"Native"},{"key":"http","label":"HTTP","variant":"HTTP"},{"key":"java","label":"Java","variant":"OkHttp"},{"key":"java","label":"Java","variant":"Unirest"},{"key":"javascript","label":"JavaScript","variant":"Fetch"},{"key":"javascript","label":"JavaScript","variant":"jQuery"},{"key":"javascript","label":"JavaScript","variant":"XHR"},{"key":"c","label":"C","variant":"libcurl"},{"key":"nodejs","label":"NodeJs","variant":"Axios"},{"key":"nodejs","label":"NodeJs","variant":"Native"},{"key":"nodejs","label":"NodeJs","variant":"Request"},{"key":"nodejs","label":"NodeJs","variant":"Unirest"},{"key":"objective-c","label":"Objective-C","variant":"NSURLSession"},{"key":"ocaml","label":"OCaml","variant":"Cohttp"},{"key":"php","label":"PHP","variant":"cURL"},{"key":"php","label":"PHP","variant":"Guzzle"},{"key":"php","label":"PHP","variant":"HTTP_Request2"},{"key":"php","label":"PHP","variant":"pecl_http"},{"key":"powershell","label":"PowerShell","variant":"RestMethod"},{"key":"python","label":"Python","variant":"http.client"},{"key":"python","label":"Python","variant":"Requests"},{"key":"r","label":"R","variant":"httr"},{"key":"r","label":"R","variant":"RCurl"},{"key":"ruby","label":"Ruby","variant":"Net::HTTP"},{"key":"shell","label":"Shell","variant":"Httpie"},{"key":"shell","label":"Shell","variant":"wget"},{"key":"swift","label":"Swift","variant":"URLSession"}],"languageOptions":[{"label":"C# - HttpClient","value":"csharp - HttpClient - C#"},{"label":"C# - RestSharp","value":"csharp - RestSharp - C#"},{"label":"cURL - cURL","value":"curl - cURL - cURL"},{"label":"Dart - http","value":"dart - http - Dart"},{"label":"Go - Native","value":"go - Native - Go"},{"label":"HTTP - HTTP","value":"http - HTTP - HTTP"},{"label":"Java - OkHttp","value":"java - OkHttp - Java"},{"label":"Java - Unirest","value":"java - Unirest - Java"},{"label":"JavaScript - Fetch","value":"javascript - Fetch - JavaScript"},{"label":"JavaScript - jQuery","value":"javascript - jQuery - JavaScript"},{"label":"JavaScript - XHR","value":"javascript - XHR - JavaScript"},{"label":"C - libcurl","value":"c - libcurl - C"},{"label":"NodeJs - Axios","value":"nodejs - Axios - NodeJs"},{"label":"NodeJs - Native","value":"nodejs - Native - NodeJs"},{"label":"NodeJs - Request","value":"nodejs - Request - NodeJs"},{"label":"NodeJs - Unirest","value":"nodejs - Unirest - NodeJs"},{"label":"Objective-C - NSURLSession","value":"objective-c - NSURLSession - Objective-C"},{"label":"OCaml - Cohttp","value":"ocaml - Cohttp - OCaml"},{"label":"PHP - cURL","value":"php - cURL - PHP"},{"label":"PHP - Guzzle","value":"php - Guzzle - PHP"},{"label":"PHP - HTTP_Request2","value":"php - HTTP_Request2 - PHP"},{"label":"PHP - pecl_http","value":"php - pecl_http - PHP"},{"label":"PowerShell - RestMethod","value":"powershell - RestMethod - PowerShell"},{"label":"Python - http.client","value":"python - http.client - Python"},{"label":"Python - Requests","value":"python - Requests - Python"},{"label":"R - httr","value":"r - httr - R"},{"label":"R - RCurl","value":"r - RCurl - R"},{"label":"Ruby - Net::HTTP","value":"ruby - Net::HTTP - Ruby"},{"label":"Shell - Httpie","value":"shell - Httpie - Shell"},{"label":"Shell - wget","value":"shell - wget - Shell"},{"label":"Swift - URLSession","value":"swift - URLSession - Swift"}],"layoutOptions":[{"value":"classic-single-column","label":"Single Column"},{"value":"classic-double-column","label":"Double Column"}],"versionOptions":[],"environmentOptions":[{"value":"0","label":"No Environment"},{"label":"Homologation","value":"40974800-bcb9599d-eda7-4b0e-a345-c127afbe3b9f"}],"canonicalUrl":"https://doc.connectpsp.com/view/metadata/2sAYQXpYm6"}