Conecte pagamentos, cobranças e assinaturas ao seu produto. Compare as documentações de autenticação, ambientes de teste e eventos antes de implementar o fluxo financeiro.
Functionality at a glance The NBG "UK OPB - Account and Transaction v3.1.5" API follows the UK Open Banking Specification v3.1.5 This Account and Transaction API Specification describes the flows and payloads for retrieving a list of accounts and their transactions.
This API is used for the classic integration. If you are just starting your implementation, refer to our new integration guide instead. The Account API provides endpoints for managing account-related entities on your platform. These related entities include account holders, accounts, bank accounts, shareholders, and verification-related documents. The management operations include actions such as creation, retrieval, updating, and deletion of them. For more information, refer to our documentation. Authentication Your Adyen contact will provide your API credential and an API key.
A flexible API for pulling accounting data, normalized and aggregated from 20 accounting integrations. Standardize how you connect to your customers’ accounting software. View, create, update, and delete data in the same way for all the leading accounting platforms. Read more... See our OpenAPI spec
The BIN Lookup API provides endpoints for retrieving information, such as cost estimates, and 3D Secure supported version based on a given BIN. Authentication You need an API credential to authenticate to the API. If using an API key, add an X-API-Key header with the API key as the value, for example: curl -H "Content-Type: application/json" \ -H "X-API-Key: YOUR_API_KEY" \ ... Alternatively, you can use the username and password to connect to the API using basic authentication, for example: curl -U "[email protected]_COMPANY_ACCOUNT":"YOUR_BASIC_AUTHENTICATION_PASSWORD" \ -H "Content-Type: application/json" \ ...
Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort). This API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit online payments documentation. Authentication Each request to Checkout API must be signed with an API key.
Adyen Data Protection API provides a way for you to process Subject Erasure Requests as mandated in GDPR. Use our API to submit a request to delete shopper's data, including payment details and other related information (for example, delivery address or shopper email).## Authentication Each request to the Data Protection API must be signed with an API key. Get your API Key from your Customer Area, as described in How to get the API key. Then set this key to the X-API-Key header value, for example: curl -H "Content-Type: application/json" \ -H "X-API-Key: Your_API_key" \ ...
A set of API endpoints that allow you to initiate, settle, and modify payments on the Adyen payments platform. You can use the API to accept card payments (including One-Click and 3D Secure), bank transfers, ewallets, and many other payment methods. To learn more about the API, visit Classic integration. Authentication You need an API credential to authenticate to the API. If using an API key, add an X-API-Key header with the API key as the value, for example: curl -H "Content-Type: application/json" \ -H "X-API-Key: YOUR_API_KEY" \ ...
A set of API endpoints that allow you to store payout details, confirm, or decline a payout. For more information, refer to Online payouts. Authentication To use the Payout API, you need to have two API credentials: one for storing payout details and submitting payouts, and another one for confirming or declining payouts. If you don't have the required API credentials, contact our Support Team.
The Recurring APIs allow you to manage and remove your tokens or saved payment details. Tokens should be created with validation during a payment request. For more information, refer to our Tokenization documentation. Authentication You need an API credential to authenticate to the API. If using an API key, add an X-API-Key header with the API key as the value, for example: curl -H "Content-Type: application/json" \ -H "X-API-Key: YOUR_API_KEY" \ ...
Introduction Welcome to the reference for the Zuora Billing REST API! To learn about the common use cases of Zuora Billing REST APIs, check out the API Guides. In addition to Zuora API Reference; Billing, we also provide API references for other Zuora products: * API Reference: Collect * API Reference: Revenue The Zuora REST API provides a broad set of operations and resources that: * Enable Web Storefront integration from your website. * Support self-service subscriber sign-ups and account management. * Process revenue schedules through custom revenue rule models. * Enable manipulation of most objects in the Zuora Billing Object Model.
[](https://app.getpostman.com/run-collection/80638214aa04722c9203) or View Postman docs Quickstart Visit github to view the quickstart tutorial. Tutorial for running the API in postman Click on ""Run in Postman"" button --- A new page will open. Click the ""Postman for windows"" to run postman as a desktop app. Make sure you have already installed Postman. --- In chrome an alert might show up to set a default app for opening postman links. Click on ""Open Postman"".
Plataforma brasileira com API para integrar a rotina de cobranças de uma empresa. A documentação inclui referência dos recursos, guias de integração e um ambiente sandbox separado da produção.
Codat's Assess API enable you to make smarter credit decisions on your small business customers. Assess enriches your customer's accounting, commerce and banking data to surface actionable insights you didn't have before. Read more... See our OpenAPI spec
Bank Feeds API enables your SMB users to set up bank feeds from accounts in your application to supported accounting platforms. A bank feed is a connection between a source bank account—in your application—and a target bank account in a supported accounting package. Read more... See our OpenAPI spec
Codat's Banking API allows you to access standardised data from over bank accounts via third party providers. Standardize how you connect to your customers’ bank accounts. Retrieve bank account and bank transaction data in the same way via our partnerships with Plaid and TrueLayer. Read more... See our OpenAPI spec
Welcome to the Big Red Cloud API This API enables programmatic access to Big Red Cloud data. We have used Swagger to auto generate the API documentation on this page, and it also enables direct interaction with the API in this page. To get started, you will require an API Key - check out our guide at https://www.bigredcloud.com/support/generating-api-key-guide/ for information on how to get one. Use the 'Enter API Key' button below to enter your API key and start interacting with your Big Red Cloud data right on this page.
The Bill Payment Validator service allows RPPS origination (payment sender) customers to identify if a potential RPPS transaction would process successfully before transmitting the formal payment transaction, reducing RPPS payment rejects and costly payment processing exceptions.
This is a Billingo API v3 documentation. Our API based on REST software architectural style. API has resource-oriented URLs, accepts JSON-encoded request bodies and returns JSON-encoded responses. To use this API you have to generate a new API key on our site. After that, you can test your API key on this page.
BIN lookup API, the free api service from bintable.com to lookup card information using it's BIN. the service maintains updated database based on the comunity and other third party services to make sure all BINs in the database are accurate and up to date.
Budgea Development Guides Welcome to Budgea's documentation. This documentation is intended to get you up-and-running with our APIs and advise on the implementation of some regulatory aspects of your application, following the DSP2's guidelines. Getting Started IMPORTANT Depending on your status with regard of the DSP2 regulation, agent or partner, you may call our APIs or simply use our Webview and callbacks to get the financial data of your users. As an agent, you are allowed to call directly our APIs and implement your own form to get the user's credentials.
*UPDATE:* *We have released a beta version of the new bunq API documentation.* *NOTICE:* *We have updated the sandbox base url to https://public-api.sandbox.bunq.com/v1/. Please update your applications accordingly. Check here: for more info.* *PSD2 NOTICE:* *The second Payment Services Directive (PSD2) may affect your current or planned usage of our public API, as some of the API services are now subject to a permit. Please be aware that using our public API without the required PSD2 permit is at your own risk and take notice of our updated API Terms and Conditions on for more information.* Introduction Welcome to bunq!
Introduction The Business Registries API is built on HTTP. The API is RESTful. It has predictable resource URIs. The API is documented in OpenAPI format. In addition to the standard OpenAPI syntax we use a few vendor extensions . Overview The following sections describe the resources that make up the Business Registries REST API. Current Version By default, all requests to https://api.abr.ato.gov.au receive the v1 version of the REST API. We encourage you to explicitly request this version via the Accept header. Accept: application/vnd.abr-ato.v1+json Schema All API access is over HTTPS, and accessed from https://api.abr.ato.gov.au.
Chaingateway.io REST API to build the bridge between Ethereum and the real world Please check out our website for detailed information about this API. To use our API, you need an API Key (Described as Authorization header in the examples below). To get one, please create an account on our website. For our internal documentation, please check out our Docs Site. If you need help with integrating our API in your application, you can reach us via email or join our official Telegram group.
>ℹ️ Check the new Checkout onboarding guide. We created this guide to improve the onboarding experience for developers at VTEX. It assembles all documentation on our Developer Portal about the Checkout and is organized by focusing on the developer's journey. The Checkout API allows you to obtain and configure information about the shopping cart and its attachments, personalization of custom fields, orderForm structure, fulfillment data, order management, and identification of the sellers delivery region. >ℹ️ Data modification operations (POST, PATCH, PUT or DELETE endpoints) shall not be performed in parallel in the Checkout APIs.
Confira versões, preços e limites diretamente na documentação de cada fornecedor.