/**
 * Adyen Checkout API
 * Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort).  This API reference provides information on available endpoints and how to interact with them. To learn more about the API, visit [Checkout documentation](https://docs.adyen.com/online-payments).  ## Authentication Each request to the Checkout API must be signed with an API key. For this, obtain an API Key from your Customer Area, as described in [How to get the API key](https://docs.adyen.com/development-resources/api-credentials#generate-api-key). Then set this key to the `X-API-Key` header value, for example:  ``` curl -H \"Content-Type: application/json\" \\ -H \"X-API-Key: Your_Checkout_API_key\" \\ ... ``` Note that when going live, you need to generate a new API Key to access the [live endpoints](https://docs.adyen.com/development-resources/live-endpoints).  ## Versioning Checkout API supports versioning of its endpoints through a version suffix in the endpoint URL. This suffix has the following format: \"vXX\", where XX is the version number.  For example: ``` https://checkout-test.adyen.com/v68/payments ```
 *
 * The version of the OpenAPI document: 68
 * Contact: developer-experience@adyen.com
 *
 * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
 * https://openapi-generator.tech
 * Do not edit the class manually.
 */ import { SplitAmount } from './splitAmount' ; export class Split { /**
    * Unique identifier of the account where the split amount should be sent. This is required if `type` is **MarketPlace** or **BalanceAccount**.
    */ 'account' ? : string ; 'amount' : SplitAmount ; /**
    * A description of this split.
    */ 'description' ? : string ; /**
    * Your reference for the split, which you can use to link the split to other operations such as captures and refunds.  This is required if `type` is **MarketPlace** or **BalanceAccount**. For the other types, we also recommend sending a reference so you can reconcile the split and the associated payment in the transaction overview and in the reports. If the reference is not provided, the split is reported as part of the aggregated [TransferBalance record type](https://docs.adyen.com/reporting/marketpay-payments-accounting-report) in Adyen for Platforms.
    */ 'reference' ? : string ; /**
    * The type of split. Possible values: **Default**, **PaymentFee**, **VAT**, **Commission**, **MarketPlace**, **BalanceAccount**.
    */ 'type' : Split . TypeEnum ; static discriminator : string | undefined = undefined ; static attributeTypeMap : Array < { name : string ; baseName : string ; type : string ; } > = [ { "name" : "account" , "baseName" : "account" , "type" : "string" } , { "name" : "amount" , "baseName" : "amount" , "type" : "SplitAmount" } , { "name" : "description" , "baseName" : "description" , "type" : "string" } , { "name" : "reference" , "baseName" : "reference" , "type" : "string" } , { "name" : "type" , "baseName" : "type" , "type" : "Split.TypeEnum" } ] ; static getAttributeTypeMap ( ) { return Split . attributeTypeMap ; } } export namespace Split { export enum TypeEnum { BalanceAccount = < any > 'BalanceAccount' , Commission = < any > 'Commission' , Default = < any > 'Default' , MarketPlace = < any > 'MarketPlace' , PaymentFee = < any > 'PaymentFee' , Vat = < any > 'VAT' , Verification = < any > 'Verification' } }