> For the complete documentation index, see [llms.txt](https://docs.exads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exads.com/ad-server/payments/saas-payments-setup.md).

# Setting Up Payments

## General Information

To set up payments and use invoice and proforma generation, Ad Server clients will need to provide the following information to their EXADS sales representative:

* Company Name
* Address
* VAT or Tax ID

## Payment Method Information

As well as the above, the Ad Server client will need to provide these additional details for each payment method that they require:

### Card Payment

**Shift4 - Card Payment (Advertisers only)**

* API Public Key
* API Secret Key

**Nuvei SafeCharge - Card Payment plus UnionPay (Advertisers only)**

* Merchant ID
* Merchant Site ID
* Merchant Secret Key
* Optionally Multi Currency Pricing is available through Nuvei. This allows Advertisers to pay in currencies other than the main currencies of the platform (USD/EUR). Please contact Nuvei to arrange this before requesting this feature with EXADS.

**Celeris - Card Payment (Advertisers only)**

* Merchant ID
* Secret Key
* SSL Cert

**IxoPay - Card Payment (Advertisers only)**

* API Username
* API Password
* API Key
* Shared Secret
* Public Integration Key

### Cryptocurrency

**Nuvei**

* Merchant ID
* Merchant Site ID
* Merchant Secret Key

**XBO**

* API Key
* Secret Key

### Wire Transfer

* Bank name
* Name on account (beneficiary)
* Bank address
* Bank country
* Account number or IBAN
* BIC or SWIFT code
* Routing number (U.S. & Canada)

### PayPal

* Client ID
* App secret

### Paxum

* Paxum email address
* Business name
* Paxum IPN key

### WebMoney

* Merchant’s purse
* WebMoney IPN key
* WebMoney USD purse
* WebMoney EUR purse

### External Payment

External Payment allows advertisers to recharge their account using an external payment provider chosen by the network.

This payment method is handled directly between the Ad Server client and their chosen payment provider. Advertisers are redirected to the configured external payment page, and funds are added to the advertiser’s account manually after payment confirmation.

To configure this payment method, the Ad Server client will need to provide:

* Title
* Link
* Instructions

{% hint style="info" %}
**Notes:**

* The system does not automatically confirm or credit these payments.
* Funds must be added manually after payment confirmation.
* The configured Link may point either to the payment provider directly or to a network-owned endpoint that initiates the payment flow.
  {% endhint %}

### Other

**Other** can be used for payments received through other means or payment methods that are unavailable on the EXADS platform, e.g. Cash, Revolut, etc. Note this payment type can only be made available to Administrator and Finance Users when creating and managing [Advertiser Transaction Types](/ad-server/payments/saas-adv-payments-tab.md#transaction-types).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.exads.com/ad-server/payments/saas-payments-setup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.