> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://support.sonas.events/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to add bank account information and set up allowed payment methods

||| If you have previously set up bank transfer details, please note that this has moved. Bank account information is no longer on its own tab and is now found under Venues, Integrations.

It is important to add your bank details for each venue, allowing clients to send you bank transfers.  These details can be added automatically into your invoice templates via tokens.

> If you cannot see this section or get permission denied messages with any of the actions, please contact your Company Admin in order to get the required permissions.

### Video:
${youtube}[](0GuLOOg3koE?si=JHfLYqRAP_hhrapi)

# How to add bank details

* Navigate to **Venues** in the main side menu, then select **Integrations**.
* Locate the **Bank Transfer** section and click the **Edit** icon.
* You will now see fields for your bank account details. These are formatted according to your country. For example, if your venue is based in New Zealand, you can leave the sort code field empty and enter all 16 digits in the account number field.
* If you have international clients, or utilise an IBAN and/or SWIFT code, add those details in the appropriate fields.
* Click **Save**.

    ![](https://storage.crisp.chat/users/helpdesk/website/-/d/5/c/e/d5ce36403ada6800/5e6b955f1ebe3bd720ce5e36164fa4_h6prg6.png)

The bank information can be added to your financial records via use of tokens, only the information provided will pull through. If you do not provide an IBAN/Swift for example, the names won't appear on the invoice.

### Primary and secondary bank accounts
Sonas now supports two bank accounts: a **primary** account and a **secondary** account.
When a customer logs into their planning portal and selects bank transfer as their payment method, they will be provided with the account details from whichever account is assigned to their event.
Use cases for a secondary account include:
* **Event type** — for example, weddings paying into your primary account and corporate events into your secondary account.
* **Domestic vs international transfers** — for example, directing foreign currency payments into a dedicated account.
|| If you have the two accounts available for an event, only the primary account will show to avoid confusion. 

### Setting default payment methods by event type
1. Navigate to your **Event Types**.
2. Under supported payment methods, select either the **main account** or **secondary account** as the default for each event type.

### Setting payment methods per event
Payment methods can also be configured on an individual event basis, overriding the default. This allows you to control, per customer, which account they pay into and which payment methods are available to them.
This also applies to **Stripe** payments. If you are using Stripe, you can specify per event type or per event whether payments can be made via Stripe, including both traditional credit card payments and the newer Stripe open banking option.
### 
Security and system logs
Any time your bank account details are edited, Sonas will automatically generate a **system log**. This is a security measure, as bank account details determine where customers are directed to send payments. We recommend keeping an eye on these logs to ensure your details remain correct.