Because our integration uses theWeb Drop-In, the new method will automatically be present on our deployed app. To do this, xcritical reviews you need to set this key to theX-API-Keyheader value when making your request. Thanks to the OpenAPI standard and theOpenAPI Generator, we’ve established a development pipeline withshorter release cyclesfor our libraries. By submitting your information you confirm that you have read xcritical’s Privacy Policy and agree to the use of your data in all xcritical communications. In the future, the Developer Dashboard will also let developers know about new releases and upcoming API changes.

1. With this comprehensive view that aggregates errors and highlights their cardinality, developers can more easily target the problems that are more critical and must be promptly prioritized.
2. We frequently release new versions of our libraries and update our APIs to offer the latest payments innovations and provide bug fixes.
3. For this, we will make a call to the `/paymentMethodSettings` endpoints, with the type of the new method we want to add.
4. Our integration will be used in the context of a catering business, and as such we will addDiners Club to the list of our allowed payment methods.
5. Each API endpoint is protected by a specific role, which is listed in the API Explorer.

Our platform supports seamless checkout experiences for various use cases, and allows you to offer unique checkout experiences with additional features. If you want to learn more about the Management API, we recommend you have a look at theAPI Explorer which gives a complete overview of the functionalities. And to get started quickly, have a look at our ready to usePostman collection.

Discover our developer resources

API and Event Logs provide the details of the requests and responses, including JSON payloads and headers. PSP references and the Request ID can be helpful to track the transactions across the platform, for example, by searching in the Transactions History screen. Of course, this blog is meant to be used as a demonstration xcritical reviews and it is likely that you would embed those capabilities as part of a middleware or a set of hardened scripts in your own context. In this article, we have discussed our approach to API Libraries and how they benefit you as a developer.

Step 2. Build your integration

Effective troubleshooting starts with a clear understanding of errors and events occurring as shoppers perform payments. The Developer Dashboard provides an overview of the most frequent API and webhook errors, allowing one to spot issues that require attention. With this comprehensive view that aggregates errors and highlights their cardinality, developers can more easily target the problems that are more critical and must be promptly prioritized.

Integration basics

To start accepting live payments using your live account, you must first configure your account. The settings from your test account are not copied to your live account. We POST a request to the /webhooks endpoint at merchant level, with the URL at which we want to receive our notifications and choose to receive our payload in the JSON format. We want to use those notifications to gather statistics about risk data, so we’ll set that additional setting to true. The next step is to create a new set, which will be used as part of the integration.

This ID can be used to further manage the payment method configuration such as allowed currencies, or countries or even disable the method altogether. To do this, we will this time perform a POST operation, on the same endpoint. In case we want to add something later on, like adding an extra origin, you can always use the available PATCH endpoint.

Each API endpoint is protected by a specific role, which is listed in the API Explorer. For example, the `/companies`endpoint requires the “Management API – Account read” role. We recommend you have a look atthe API Explorer for an exhaustive list of the API capabilities, but note that the set of functionalities presented here is only a subset of what is available.

First and foremost, let’s have a look whether our set of credentials actually works fine. We’ll be calling the ‘/me’ endpoint to obtain information about our account. First, we need to create a new API credential with the required roles, just that one time so we don’t have to in the future. Alright, let’s set up a sample integration without having to log in our Customer Area, using the Management API. To do this, we will perform the same steps as we would form the customer area.

With the Developer Dashboard, you can have a visual overview of the integration status at all times. Applying the available filters and groups makes it possible to pinpoint when the issue began and assess its impact. Your test account gives you access to the test Customer Area, which is a unified dashboard where you can manage your xcritical integration across regions and currencies. We are very much looking forward to hearing about your automation use cases, and what type of other resources you would like to see made available.