You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For APIS that require your [Live URL Prefix](https://docs.adyen.com/development-resources/live-endpoints#live-url-prefix) (Binlookup, BalanceControl, Checkout, Payout and Recurring) the client is set up as follows in order to start processing live payments:
By default, [Node.js https](https://nodejs.org/api/https.html) is used to make API requests. Alternatively, you can set a custom `HttpClient` for your `Client` object.
267
267
268
+
**Note**: when using your custom `HttpClient`, you must define all required properties (API key, content-type, timeouts, etc..)
In order to submit In-Person requests with [Terminal API over Cloud](https://docs.adyen.com/point-of-sale/design-your-integration/choose-your-architecture/cloud/) you need to initialize the client in a similar way as the steps listed above for Ecommerce transactions, but make sure to include `TerminalCloudAPI`:
341
+
### Using the Cloud Terminal API
342
+
For In-Person Payments integrations with the [Cloud Terminal API](https://docs.adyen.com/point-of-sale/design-your-integration/choose-your-architecture/cloud/), you must initialise the Client **setting the closest**[Region](https://docs.adyen.com/point-of-sale/design-your-integration/terminal-api/#cloud):
341
343
```javascript
342
344
// Step 1: Require the parts of the module you want to use
343
345
const {Client, TerminalCloudAPI} from "@adyen/api-library";
0 commit comments