### QuickPay API Request Examples

Source: https://learn.quickpay.net/tech-talk/api

Demonstrates how to make PUT and GET requests to the QuickPay API, including essential headers like Host, Authorization, Accept-Version, and Accept. The PUT request example also shows how to send data in the request body.

```HTTP
PUT /resource/<Identifier> HTTP/1.1
Host: api.quickpay.net
Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==
Accept-Version: v10
Accept: application/json
key1=value1&key2=value2


```

```HTTP
GET /resource/<Identifier> HTTP/1.1
Host: api.quickpay.net
Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==
Accept-Version: v10
Accept: application/json


```

--------------------------------

### QuickPay API Ping Example

Source: https://learn.quickpay.net/tech-talk/api/services_scope=merchant

Example of how to ping the QuickPay API using curl to check connectivity and API version.

```bash
$ curl -v -su '' -H 'Accept-Version: v10' https://api.quickpay.net/ping
Enter host password for user '': <enter your api key here>
```

--------------------------------

### Example API Response for Recurring Payment

Source: https://learn.quickpay.net/tech-talk/guides/subscriptions

This is an example of a successful response from the QuickPay API when creating a recurring payment. It includes the payment ID, merchant ID, order ID, and the initial state of the payment, which is typically 'pending'.

```APIDOC
{
  "id": 97629687,
  "merchant_id": 1234,
  "order_id": "rec10001",
  "accepted": false,
  "type": "Payment",
  "state": "pending"
}
```

--------------------------------

### Ping API Endpoint Example

Source: https://learn.quickpay.net/tech-talk/api/services

Example of how to ping the QuickPay API using curl to check connectivity and API version compatibility. Requires an API key for authorization.

```bash
$ curl -v -su '' -H 'Accept-Version: v10' https://api.quickpay.net/ping
Enter host password for user '': <enter your api key here>
```

--------------------------------

### Example cURL Request for Payment Status

Source: https://learn.quickpay.net/tech-talk/guides/payments

An example of how to use cURL to make a GET request to the QuickPay API to check the status of a payment.

```bash
curl -u ':APIKEY' \
     -H 'content-type:application/json' \
     -H 'Accept-Version:v10' \
     -X GET \
     https://api.quickpay.net/payments/99685196
```

--------------------------------

### Example cURL Request for Recurring Payment

Source: https://learn.quickpay.net/tech-talk/guides/subscriptions

This snippet demonstrates how to make a POST request to the QuickPay API to create a recurring payment using cURL. It includes necessary headers like content-type and Accept-Version, and the request body with amount and order_id.

```bash
curl -u ':APIKEY' \
	   -H 'content-type:application/json' \
	   -H 'Accept-Version:v10' \
	   -X POST \
	   -d '{"amount":1000,"order_id":"rec10001"}' \
	   https://api.quickpay.net/subscriptions/97629173/recurring
```

--------------------------------

### QuickPay API Response Body Examples

Source: https://learn.quickpay.net/tech-talk/api

Illustrates the structure of JSON response bodies for QuickPay API requests. It shows examples for successful single resource retrieval, successful list retrieval, and error responses, highlighting common keys like 'message', 'errors', and 'error_code'.

```HTTP
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Content-Length: nnn

{
  "key1": "value1",
  "key2": "value2"
}


```

```HTTP
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Content-Length: nnn

[
  {
    "key1": "value1",
    "key2": "value2"
  },
  {
    "key1": "value1",
    "key2": "value2"
  }
]


```

```HTTP
HTTP/1.1 400 Bad Request
Content-Type: application/json; charset=UTF-8
Content-Length: nnn

{
  "message": "Validation error",
  "errors": {
    "key1": ["is required", "must be at least 5 chars"]
  },
  "error_code": null
}


```

--------------------------------

### UnzerPayLater Acquirer Settings API

Source: https://learn.quickpay.net/tech-talk/api/services

Provides details for GET requests related to UnzerPayLater acquirer settings.

```APIDOC
GET /acquirers/unzerpaylater
  Description: Get UnzerPayLater acquirer settings
```

--------------------------------

### Contributing to QuickPay Projects

Source: https://learn.quickpay.net/tech-talk/opensource

A step-by-step guide on how to contribute to QuickPay's open-source projects using Git and GitHub Pull Requests.

```Git
1. Fork the project ( https://github.com/QuickPay/<project>/fork )
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Add some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create a new Pull Request
```

--------------------------------

### Quickpay API Introduction and Usage

Source: https://learn.quickpay.net/tech-talk

This section provides an introduction to the Quickpay API, outlining the primary methods for accepting payments: Quickpay Link and Quickpay Form. It also mentions the availability of a Postman Collection for testing the API.

```APIDOC
API:
  Introduction: https://learn.quickpay.net/tech-talk/api/
  Services: https://learn.quickpay.net/tech-talk/api/services
  Callback: https://learn.quickpay.net/tech-talk/api/callback

Payment Methods:
  Quickpay Link: https://learn.quickpay.net/tech-talk/payments/link/
  Quickpay Form: https://learn.quickpay.net/tech-talk/payments/form/

Postman Collection: https://app.getpostman.com/run-collection/35600e19e57d16b0221b

Support:
  FAQ and Helpdesk: https://quickpay.net/helpdesk/
  Email: support@quickpay.net
```

--------------------------------

### Create Quickpay Link - Ruby

Source: https://learn.quickpay.net/tech-talk/payments/link

Demonstrates how to create a Quickpay Link using the quickpay-ruby-client gem. It covers creating a payment and then a link for that payment, outputting the generated URL.

```Ruby
# Use the official quickpay-ruby-client gem
require "quickpay/api/client"
client = QuickPay::API::Client.new(password: ENV['YOUR_API_USER_KEY'])

# /framed requests require: `allow-same-origin`, `allow-scripts` and `allow-forms` headers.
payment = client.post(
    "/payments",
    headers: { "Content-Type" => "application/json" },
    body: { order_id: "0001", currency: "DKK" }.to_json
  )

link = client.put(
    "/payments/#{payment['id']}/link",
    headers: { "Content-Type" => "application/json" },
    body: { amount: 100 }.to_json
  )

puts link['url']
```

--------------------------------

### Get Payout Status API

Source: https://learn.quickpay.net/tech-talk/guides/payouts

Retrieves the status of a specific payout using its ID. This is used to confirm if the payout has been successfully processed.

```APIDOC
GET /payouts/{id}
  Get payout
  Last step is to check the status of the payout.
  This could be on a continue-url, where you render a “Payout successful”-message when the payout is complete.
  #### Example request:
  ```
  curl -u ':APIKEY' \
       -H 'content-type:application/json' \
       -H 'Accept-Version:v10' \
       -X GET \
       https://api.quickpay.net/payouts/99685805
  ```
```

--------------------------------

### Quickpay API Overview

Source: https://learn.quickpay.net/tech-talk/api

Provides an introduction to the Quickpay API, its RESTful nature, and recommended reading on related web technologies like HTTP, Headers, REST, and JSON.

```APIDOC
The Quickpay API is based on the principles of Representational State Transfer (REST) allowing clients to create, view, modify and delete resources using standard HTTP request methods.
Recommended reading:
  * HTTP: <http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol>
  * Headers: <http://en.wikipedia.org/wiki/List_of_HTTP_headers>
    * Basic access authentication: <http://en.wikipedia.org/wiki/Basic_access_authentication>
    * Status codes: <http://en.wikipedia.org/wiki/List_of_HTTP_status_codes>
  * REST: <http://en.wikipedia.org/wiki/Representational_State_Transfer>
  * JSON: <http://en.wikipedia.org/wiki/JSON>

The Quickpay API is purposely the service upon which everything else in Quickpay is built ([we eat our own dog food](http://en.wikipedia.org/wiki/Eating_your_own_dog_food)).
```

--------------------------------

### C# QuickPay Payment Setup

Source: https://learn.quickpay.net/tech-talk/payments/form

Demonstrates how to set up payment parameters in C# for QuickPay. It includes adding various details like merchant ID, order ID, amount, currency, and URLs for continuation, cancellation, and callbacks. It also shows how to generate a checksum using a secret API key.

```C#
public ActionResult QuickPay() {
    var params = new Dictionary<string, string>();
    params.Add("version", "v10");
    params.Add("merchant_id", "1");
    params.Add("agreement_id", "1");
    params.Add("order_id", "0001");
    params.Add("amount", "100");
    params.Add("currency", "DKK");
    params.Add("continueurl", "http://shop.domain.tld/continue");
    params.Add("cancelurl", "http://shop.domain.tld/cancel");
    params.Add("callbackurl", "http://shop.domain.tld/callback");
    params.Add("language", "da");
    params.Add("autocapture", "1");

    ViewBag.Language = language;
    ViewBag.Autocapture = autocapture;
    ViewBag.OrderId = orderId;
    ViewBag.MerchantId = merchantId;
    ViewBag.AgreementId = agreementId;
    ViewBag.Amount = amount;
    ViewBag.Currency = currency;
    ViewBag.ContinueUrl = continueUrl;
    ViewBag.CancelUrl = cancelUrl;
    ViewBag.CallbackUrl = callbackUrl;
    ViewBag.Checksum = Sign(params, "your_secret_payment_window_api_key");

    return View();
}
```

--------------------------------

### GET /changelog - Get API Changelog

Source: https://learn.quickpay.net/tech-talk/api/services

Retrieves the API changelog. Requires API version. Supports optional authorization.

```APIDOC
GET /changelog

Request Parameters:
- Accept-Version (header, string, required): Specify the version of the API
- Authorization (header, string, optional): Use Basic Auth to authorize to the API

Response Messages:
- 200 OK
```

--------------------------------

### GET /payments - Get All Payments

Source: https://learn.quickpay.net/tech-talk/api/services

Retrieves a list of all payments. Specific request parameters and response details are not provided in this documentation snippet.

```APIDOC
GET /payments

Description: Get all payments
```

--------------------------------

### GET /acquirers/coinify - Get Coinify Acquirer Settings

Source: https://learn.quickpay.net/tech-talk/api/services

Retrieves the current settings for the Coinify acquirer. Requires API version and authorization headers.

```APIDOC
GET /acquirers/coinify
  Description: Get Coinify acquirer settings
  Request Headers:
    Accept-Version: Specify the version of the API (string, required)
    Authorization: Use Basic Auth to authorize to the API (string, required)
  Response Codes:
    200: OK
    403: Not authorized
```

--------------------------------

### Create Payment and Link (PHP)

Source: https://learn.quickpay.net/tech-talk/payments/link

This PHP snippet demonstrates how to use the QuickPay client to create a payment and subsequently generate a payment link. It initializes the client with an API key, creates a payment specifying currency and order ID, and then generates a payment link with a given amount. Error handling is included for successful creation of both the payment and the link.

```php
<?php
use QuickPay\QuickPay;

try {
    //Initialize client
    $client = new QuickPay(":api-key-here");

    //Create payment
    $payment = $client->request->post('/payments', [
        'order_id' => '0007',
        'currency' => 'DKK',
    ]);

    $status = $payment->httpStatus();

    //Determine if payment was created successfully
    if ($status === 201) {

        $paymentObject = $payment->asObject();

        //Construct url to create payment link
        $endpoint = sprintf("/payments/%s/link", $paymentObject->id);

        //Issue a put request to create payment link
        $link = $client->request->put($endpoint, [
            'amount' => 100 //amount in cents
        ]);

        //Determine if payment link was created succesfully
        if ($link->httpStatus() === 200) {
            //Get payment link url
            echo $link->asObject()->url;
        }
    }
} catch (\Exception $e) {
    echo $e->getMessage();
}
?>
```

--------------------------------

### Ruby QuickPay API Client Usage

Source: https://learn.quickpay.net/tech-talk/guides/cards

Demonstrates how to initialize the QuickPay API client in Ruby and make requests to create card tokens, initiate payments, and authorize payments.

```ruby
require "quickpay/api/client"
client = QuickPay::API::Client.new(password: ENV["QUICKPAY_API_KEY"])

tokens  = client.post("/cards/#{card['id']}/tokens")

payment = client.post(
  "/payments",
  headers: { "Content-Type" => "application/json" },
  body: {
    order_id: "0001",
    currency: "DKK"
  }.to_json
)

authorize = client.post(
  "/payments/#{payment['id']}/authorize",
  headers: { "Content-Type" => "application/json" },
  query: { "synchronized" => "" },
  body: {
    amount: 100,
    card: { token: tokens['token'] }
  }.to_json
)
```

--------------------------------

### GET /acquirers/clearhaus - Get Clearhaus Acquirer Settings

Source: https://learn.quickpay.net/tech-talk/api/services

Retrieves the current settings for the Clearhaus acquirer. Requires API version and authorization headers.

```APIDOC
GET /acquirers/clearhaus
  Description: Get Clearhaus acquirer settings
  Request Headers:
    Accept-Version: Specify the version of the API (string, required)
    Authorization: Use Basic Auth to authorize to the API (string, required)
  Response Codes:
    200: OK
    403: Not authorized
```

--------------------------------

### Python QuickPay API Client Usage

Source: https://learn.quickpay.net/tech-talk/guides/cards

Demonstrates how to initialize the QuickPay API client in Python and make requests to create card tokens, initiate payments, and authorize payments.

```python
from quickpay_api_client import QPClient
import os

secret = ":{%s}".format(os.environ['QUICKPAY_API_KEY'])
client = QPClient(secret)

tokens    = client.post("/cards/%s/tokens" % card['id'])
payment   = client.post("/payment", body={'currency':"DKK", 'order_id': "0001"})
authorize = client.post("/payments/%s/authorize?synchronized" % payment['id'],
                        body={'amount=100'},
                        card={"token": tokens['token']})
```

--------------------------------

### GET /subscriptions/{id} - Get subscription

Source: https://learn.quickpay.net/tech-talk/api/services

Retrieves details of a subscription. Supports specifying the API version, authorization, subscription ID, and the number of operations to retrieve.

```APIDOC
GET /subscriptions/{id}

Description: Get subscription

Request Parameters:
Parameter | Description | Parameter Type | Data Type | Default | Required?
---|---|---|---|---|---
Accept-Version | Specify the version of the API | header | string |  | true
Authorization | Use Basic Auth to authorize to the API | header | string |  | true
id | Subscription id | path | array |  | true
operations_size | Maximum number of operations to retrieve | query | integer |  | false

Response Messages:
HTTP Status Code | Reason
---|---
200 | OK
403 | Not authorized
404 | Not found
```

--------------------------------

### Create Payment and Link (Python)

Source: https://learn.quickpay.net/tech-talk/payments/link

This Python snippet shows how to use the QuickPay client to create a new payment and then generate a payment link for it. It requires the QUICKPAY_API_KEY environment variable to be set for authentication. The payment is created with a currency and order ID, and the link is generated with a specific amount.

```python
# -*- coding: utf-8 -*-
import os
from quickpay_api_client import QPClient

secret = ':{0}'.format(os.environ['QUICKPAY_API_KEY'])
client = QPClient(secret)

payment = client.post('/payments', body={'currency': 'DKK',
                      'order_id': '0001'})

link = client.put('/payments/%s/link' % payment['id'],
                  body={'amount': 100})

  # Add framed=true if you want to open in an iframe

print link['url']
```

--------------------------------

### GET /cryptography/keys - Get Cryptography Keys

Source: https://learn.quickpay.net/tech-talk/api/services

Retrieves a list of cryptographic keys. Supports filtering by type, query, sorting, and pagination. Requires API version and authorization.

```APIDOC
GET /cryptography/keys

Request Parameters:
- Accept-Version (header, string, required): Specify the version of the API
- Authorization (header, string, required): Use Basic Auth to authorize to the API
- type (query, string (ec, rsa), optional): Filter by key type
- query (query, string, optional): General query parameter
- sort_by (query, string (id), optional, default: id): Property to sort by
- sort_dir (query, string (asc, desc), optional, default: desc): Sort direction
- page_size (query, integer, optional, default: 20): Items per page
- page_key (query, integer, optional): Pagination key

Response Messages:
- 200 OK
- 403 Not authorized

MerchantCryptographyKey Model:
- id (integer): KMS id
- type (string): Key type (ec/rsa)
- short_description (string): Short description
- certificate_expires_at (ISO-8601): Certificate expiration timestamp
- public_key_hash (string): Public Key identification hash
- created_at (ISO-8601): Timestamp of creation
- updated_at (ISO-8601): Timestamp of update
```

--------------------------------

### QuickPay API Clients

Source: https://learn.quickpay.net/tech-talk/opensource

Links to QuickPay's official API client libraries for popular programming languages, including source code repositories, issue trackers, and package manager links.

```PHP
PHP Client:
  Source: https://github.com/QuickPay/quickpay-php-client
  Issues: https://github.com/QuickPay/quickpay-php-client/issues
  Composer: https://packagist.org/packages/quickpay/quickpay-php-client
```

```Ruby
Ruby Client:
  Source: https://github.com/QuickPay/quickpay-ruby-client
  Issues: https://github.com/QuickPay/quickpay-ruby-client/issues
  Rubygems: https://rubygems.org/gems/quickpay-ruby-client
```

```Python
Python Client:
  Source: https://github.com/QuickPay/quickpay-python-client
  Issues: https://github.com/QuickPay/quickpay-python-client/issues
  PyPI: https://pypi.python.org/pypi/quickpay-api-client
```

```.NET
.Net Client:
  Source: https://github.com/QuickPay/quickpay-dotnet-client
  Issues: https://github.com/QuickPay/quickpay-dotnet-client/issues
  NuGet: https://www.nuget.org/packages/QuickPay.API.Client/1.0.0
```

--------------------------------

### Payment Method Syntax and Examples

Source: https://learn.quickpay.net/tech-talk/appendixes/payment-methods

Defines the syntax for specifying payment methods, including brand, issuing country, and security level. Provides an example of a restricted Mastercard payment.

```APIDOC
Payment Method Syntax:
`[3d-]{brand}[-{ISO 3166-1 alpha-2}][-business]`

Example:
`3d-mastercard-dk-business`
- `3d-`: Signifies 3D Secure.
- `mastercard`: The Brand (e.g., Visa, Mastercard).
- `dk`: Issuing country as ISO 3166-1 alpha-2.
- `business`: Signifies a corporate card.
```

--------------------------------

### Create Subscription API

Source: https://learn.quickpay.net/tech-talk/guides/subscriptions

Creates a new subscription entity in Quickpay. Requires a unique order ID, currency, and description. Returns the created subscription object.

```APIDOC
POST /subscriptions
  Create subscription
  First step is to create a new subscription entity in Quickpay.
  On a new subscription you are required to include a unique order id, the currency and a description of the subscription.
  Selected parameters. [See more in the API documentation](https://learn.quickpay.net/tech-talk/api/services/#POST-subscriptions---format-).
  Parameter | Description | Parameter type | Data type | Required?
  ---|---|---|---|---
  order_id | Unique order number | form | string | true
  currency | Currency | form | string | true
  description | Subscription description | form | string | true
  Example response (snippet):
  {"id":97629173,"merchant_id":1234,"order_id":"sub10004","accepted":false,"type":"Subscription","currency":"EUR","state":"initial"...}
```

```bash
curl -u ':APIKEY' \
     -H 'content-type:application/json' \
     -H 'Accept-Version:v10' \
     -X POST \
     -d '{"order_id":"sub10003","currency":"eur","description":"shoe-sub"}' \
     https://api.quickpay.net/subscriptions
```

--------------------------------

### GET /cards/{id}/operations/{operation_id} - Get Operation

Source: https://learn.quickpay.net/tech-talk/api/services

Retrieves a specific card operation by its ID. Requires API version and authorization. Supports path parameters for card and operation IDs.

```APIDOC
GET /cards/{id}/operations/{operation_id}

Request Parameters:
- Accept-Version (header, string, required): Specify the version of the API
- Authorization (header, string, required): Use Basic Auth to authorize to the API
- operation_id (path, integer, required): Operations id
- id (path, string, optional): 

Response Messages:
- 200 OK
- 403 Not authorized
- 404 Not found

CardOperation Model:
- id (integer): Operation ID
- type (string): Type of operation
- pending (boolean): If the operation is pending
- qp_status_code (string): QuickPay status code
- qp_status_msg (string): QuickPay status message
- aq_status_code (string): Acquirer status code
- aq_status_msg (string): Acquirer status message
- data (hash): Acquirer specific data
- callback_url (string): Operation callback url
- callback_success (boolean): Did the callback succeed
- callback_response_code (string): The http response code from the callback operation
- callback_duration (integer): Callback duration (ms)
- acquirer (string): Acquirer that processed this operation
- callback_at (ISO-8601): Timestamp of callback
- created_at (ISO-8601): Timestamp of creation
```

--------------------------------

### GET /acquirers/swedbank - Get Swedbank Acquirer Settings

Source: https://learn.quickpay.net/tech-talk/api/services

Retrieves the current settings for the Swedbank acquirer. Requires API version and authorization headers. Returns detailed configuration parameters for Swedbank payments.

```APIDOC
GET /acquirers/swedbank
  Description: Get Swedbank acquirer settings
  Request Headers:
    Accept-Version: Specify the version of the API (string, required)
    Authorization: Use Basic Auth to authorize to the API (string, required)
  Response Messages:
    200: OK
    403: Not authorized
  AcquirerSettings::Swedbank Model:
    active: True if the acquirer is active (boolean)
    identification_code: Swedbank identification number (string)
    identification_code_int: Swedbank international identification number (string)
    business_code: Swedbank business code (string)
    recurring: True if recurring is enabled (boolean)
    americanexpress: True if american express is enabled (boolean)
    dinersclub: True if Diners Club is enabled (boolean)
    securepay: True if Teller SecurePay fraud detection is enabled (boolean)
    visa_mpi_merchant_id: VISA MPI Merchant id used for 3D Secure (string)
    mastercard_mpi_merchant_id: Mastercard MPI Merchant id used for 3D Secure (string)
    visa_bin: Swedbank VISA acquirer bin used for 3D Secure (string)
    mastercard_bin: Swedbank Mastercard acquirer bin used for 3D Secure (string)
    local_tz: Local timezone of the merchant, described as tz database name (string)
```

--------------------------------

### QuickPay API - Get Saved Card Endpoint

Source: https://learn.quickpay.net/tech-talk/api/services_scope=merchant

Details the GET request to retrieve information about a saved card. Includes required headers, path parameters, and possible HTTP status codes for responses.

```APIDOC
GET /cards/{id}:
  Description: Get saved card
  Parameters:
    Headers:
      Accept-Version: Specify the version of the API (string, required)
      Authorization: Use Basic Auth to authorize to the API (string, required)
    Path:
      id: Card identifier (string, optional)
  Responses:
    200: OK
    403: Not authorized
    404: Not found
```

--------------------------------

### IntegrationSettings::Shopify Model Parameters

Source: https://learn.quickpay.net/tech-talk/api/services

Defines the settings for integrating with Shopify, including activation status, access token, and shop domain.

```APIDOC
IntegrationSettings::Shopify Model:
  active: True if the settings are active (boolean)
  access_token: Shopify App: store access token (string)
  shop_domain: Shopify App: store domain name (string)
```

--------------------------------

### GET /payment-method-priority - Get Merchant Payment Method Priority

Source: https://learn.quickpay.net/tech-talk/api/services

Retrieves the payment method priority settings for a merchant. Requires API version and authorization headers. Returns 200 OK on success or 403 if not authorized.

```APIDOC
GET /payment-method-priority

Request Parameters:
  Accept-Version: string (header, required)
  Authorization: string (header, required)

Response Messages:
  200: OK
  403: Not authorized

Models:
  PaymentMethodPriority: { payment_method_priority: hash }
```

--------------------------------

### IntegrationSettings Model

Source: https://learn.quickpay.net/tech-talk/api/services

Defines the structure for integration settings, including configurations for e-conomic and Shopify.

```APIDOC
IntegrationSettings Model:
  economic: e-conomic settings (IntegrationSettings::Economic)
  shopify: ShopifyApp store settings (IntegrationSettings::Shopify)
```

--------------------------------

### GET /acquirers/swish - Get Swish Acquirer Settings

Source: https://learn.quickpay.net/tech-talk/api/services

Retrieves the current Swish acquirer settings. Requires API version and authorization headers. Returns OK (200) on success or Not authorized (403) if authentication fails.

```APIDOC
GET /acquirers/swish
  Description: Get Swish acquirer settings
  Headers:
    Accept-Version: Specify the version of the API (string, required)
    Authorization: Use Basic Auth to authorize to the API (string, required)
  Responses:
    200: OK
    403: Not authorized
```

--------------------------------

### GET /acquirers/teller - Get Teller Acquirer Settings

Source: https://learn.quickpay.net/tech-talk/api/services

Retrieves the current Teller acquirer settings. Requires API version and authorization headers. Returns OK (200) on success or Not authorized (403) if authentication fails.

```APIDOC
GET /acquirers/teller
  Description: Get Teller acquirer settings
  Headers:
    Accept-Version: Specify the version of the API (string, required)
    Authorization: Use Basic Auth to authorize to the API (string, required)
  Responses:
    200: OK
    403: Not authorized
```

--------------------------------

### IntegrationSettings::Economic Model Parameters

Source: https://learn.quickpay.net/tech-talk/api/services_scope=merchant

Defines the e-conomic integration settings, including activation status, agreement ID, and agreement token.

```APIDOC
IntegrationSettings::Economic Model:
  active: True if the settings are active (boolean)
  agreement: e-conomic agreement id (string)
  agreement_token: e-conomic agreement grant token (string)
```

--------------------------------

### AcquirerSettings::UnzerPayLater Model Parameters

Source: https://learn.quickpay.net/tech-talk/api/services

Details the configuration for the UnzerPayLater acquirer, enabling specific payment methods like Invoice, Instalment, and Direct Debit, each with their own credentials.

```APIDOC
AcquirerSettings::UnzerPayLater Model:
  active: True if the acquirer is active (boolean)
  invoice: Unzer Pay Later credentials for Invoice transactions (AcquirerSettings::UnzerPayLater::PaymentMethod)
  instalment: Unzer Pay Later credentials for Instalment transactions (AcquirerSettings::UnzerPayLater::PaymentMethod)
  direct_debit: Unzer Pay Later credentials for Direct Debit transactions (AcquirerSettings::UnzerPayLater::PaymentMethod)
```

--------------------------------

### Get Valitor Acquirer Settings

Source: https://learn.quickpay.net/tech-talk/api/services

Retrieves the current settings for the Valitor acquirer.

```APIDOC
GET /acquirers/valitor

Request Parameters:
  Accept-Version: Specify the version of the API (header, string, required)
  Authorization: Use Basic Auth to authorize to the API (header, string, required)

Response Messages:
  200: OK
  403: Not authorized
```

--------------------------------

### AcquirerSettings::Sofort Model Parameters

Source: https://learn.quickpay.net/tech-talk/api/services

Outlines the configuration parameters for the Sofort payment acquirer, including general settings, API keys, and specific iDeal configurations.

```APIDOC
AcquirerSettings::Sofort:
  active: True if the acquirer is active (boolean)
  customer_number: Sofort customer number (integer)
  project_id: Sofort gateway project id (integer)
  api_key: Sofort api-key (string)
  gateway: Sofort gateway feature enabled (boolean)
  ideal: Sofort iDeal feature enabled (boolean)
  ideal_project_id: Sofort iDeal project id (integer)
  ideal_project_password: Sofort iDeal project password (string)
  ideal_notification_password: Sofort iDeal notification password (string)
```

--------------------------------

### GET /subscriptions

Source: https://learn.quickpay.net/tech-talk/api/services

Retrieves a list of all subscriptions. This endpoint requires API version and authorization headers.

```APIDOC
GET /subscriptions
  Description: Get subscriptions
  Headers:
    Accept-Version: Specify the version of the API (string, required)
    Authorization: Use Basic Auth to authorize to the API (string, required)
```

--------------------------------

### IntegrationSettings::Economic Model Parameters

Source: https://learn.quickpay.net/tech-talk/api/services_scope=merchant

Defines the e-conomic integration settings, including activation status, agreement ID, and agreement token.

```APIDOC
IntegrationSettings::Economic Model:
  active: True if the settings are active (boolean)
  agreement: e-conomic agreement id (string)
  agreement_token: e-conomic agreement grant token (string)
```

--------------------------------

### Get Payouts

Source: https://learn.quickpay.net/tech-talk/api/services_scope=merchant

Retrieves a list of payouts. Further details on parameters and response structure are not provided in this snippet.

```APIDOC
GET /payouts
```