import RestClient from "../restClient.js";
import type { GetSplitsOptions, TransactionSplitCreatePayload, UpdateTxSplitPayload } from "../types/clients/index.js";
import type { PaystackResponse } from "../types/global.js";
import type { TransactionSplit } from "../types/models.js";
/**
 * TransactionSplitClient provides methods lets you interface with Paystack's
 * Transaction Splits API which enables merchants split the settlement for a transaction
 * across their payout account, and one or more Subaccounts.
 * https://paystack.com/docs/api/split/
 */
export default class TransactionSplitClient {
    private client;
    /**
     * @constructor Instantiate a TransactionSplitClient
     *
     * @param secretKey - Your paystack integration secret key.
     * @param client - A custom rest client to use for making api calls to paystack's instead
     * of creating a new one with the secretKey
     */
    constructor(secretKey?: string, client?: RestClient);
    /**
     * Create a split payment on your integration
     *
     * @remarks
     *
     * For typescript users, you may experience inconsistencies in the returned data such as
     * the data returned doesn't match the method return type or the data returned has
     * more fields that are not showing up or flagged as errors. This is because no validation
     * is done to check if the actual returned data matches the return type. The returned data
     * is just cast as the return type. Also, the return types are based on the seen data as at
     * the time of implementation and are subject to errors and changes from paystack (e.g.,
     * paystack adding more fields, which makes the models incorrect). When faced with this issue
     * in development, you may cast the method return type as `any` and then cast is to a return
     * type that serves your purpose. Also, please create an issue for it at
     * https://github.com/gray-adeyi/paystack-sdk/issues so the issue is fixed in future releases.
     *
     * @param payload - {@link TransactionSplitCreatePayload} is the data sent to
     * paystack to create a transaction split.
     * @returns A promise that resolves to an object whose type is {@link PaystackResponse}.
     * The data property of the object is another object of type {@link TransactionSplit}
     */
    create(payload: TransactionSplitCreatePayload): Promise<PaystackResponse<TransactionSplit>>;
    /**
     * Get/search for the transaction splits available on your integration.
     *
     * @remarks
     *
     * For typescript users, you may experience inconsistencies in the returned data such as
     * the data returned doesn't match the method return type or the data returned has
     * more fields that are not showing up or flagged as errors. This is because no validation
     * is done to check if the actual returned data matches the return type. The returned data
     * is just cast as the return type. Also, the return types are based on the seen data as at
     * the time of implementation and are subject to errors and changes from paystack (e.g.,
     * paystack adding more fields, which makes the models incorrect). When faced with this issue
     * in development, you may cast the method return type as `any` and then cast is to a return
     * type that serves your purpose. Also, please create an issue for it at
     * https://github.com/gray-adeyi/paystack-sdk/issues so the issue is fixed in future releases.
     *
     * @param options - {@link GetSplitsOptions} lets you customize the data
     * to be returned in the response.
     * @returns A promise that resolves to an object whose type is {@link PaystackResponse}.
     * The data property of the object is an array of objects of type {@link TransactionSplit}
     */
    getSplits(options?: GetSplitsOptions): Promise<PaystackResponse<TransactionSplit[]>>;
    /**
     * Get details of a split on your integration.
     *
     * @remarks
     *
     * For typescript users, you may experience inconsistencies in the returned data such as
     * the data returned doesn't match the method return type or the data returned has
     * more fields that are not showing up or flagged as errors. This is because no validation
     * is done to check if the actual returned data matches the return type. The returned data
     * is just cast as the return type. Also, the return types are based on the seen data as at
     * the time of implementation and are subject to errors and changes from paystack (e.g.,
     * paystack adding more fields, which makes the models incorrect). When faced with this issue
     * in development, you may cast the method return type as `any` and then cast is to a return
     * type that serves your purpose. Also, please create an issue for it at
     * https://github.com/gray-adeyi/paystack-sdk/issues so the issue is fixed in future releases.
     *
     * @param id - The id of the split.
     * @returns A promise that resolves to an object whose type is {@link PaystackResponse}.
     * The data property of the object is another object of type {@link TransactionSplit}
     */
    getSplit(id: string): Promise<PaystackResponse<TransactionSplit>>;
    /**
     * Update a transaction split details on your integration
     *
     * @remarks
     *
     * For typescript users, you may experience inconsistencies in the returned data such as
     * the data returned doesn't match the method return type or the data returned has
     * more fields that are not showing up or flagged as errors. This is because no validation
     * is done to check if the actual returned data matches the return type. The returned data
     * is just cast as the return type. Also, the return types are based on the seen data as at
     * the time of implementation and are subject to errors and changes from paystack (e.g.,
     * paystack adding more fields, which makes the models incorrect). When faced with this issue
     * in development, you may cast the method return type as `any` and then cast is to a return
     * type that serves your purpose. Also, please create an issue for it at
     * https://github.com/gray-adeyi/paystack-sdk/issues so the issue is fixed in future releases.
     *
     * @param id - The split id
     * @param payload - {@link UpdateTxSplitPayload} is the data used to
     * update the transaction split.
     * @returns A promise that resolves to an object whose type is {@link PaystackResponse}.
     * The data property of the object is another object of type {@link TransactionSplit}
     */
    update(id: string, payload: UpdateTxSplitPayload): Promise<PaystackResponse<TransactionSplit>>;
    /**
     * Add a Subaccount to a Transaction Split, or update
     * the share of an existing Subaccount in a Transaction Split
     *
     * @remarks
     *
     * For typescript users, you may experience inconsistencies in the returned data such as
     * the data returned doesn't match the method return type or the data returned has
     * more fields that are not showing up or flagged as errors. This is because no validation
     * is done to check if the actual returned data matches the return type. The returned data
     * is just cast as the return type. Also, the return types are based on the seen data as at
     * the time of implementation and are subject to errors and changes from paystack (e.g.,
     * paystack adding more fields, which makes the models incorrect). When faced with this issue
     * in development, you may cast the method return type as `any` and then cast is to a return
     * type that serves your purpose. Also, please create an issue for it at
     * https://github.com/gray-adeyi/paystack-sdk/issues so the issue is fixed in future releases.
     *
     * @param id - the split ID
     * @param subaccount - The subaccount code.
     * @param share - This is the transaction share for the subaccount
     * @returns A promise that resolves to an object whose type is {@link PaystackResponse}.
     * The data property of the object is another object of type {@link TransactionSplit}
     */
    addOrUpdate(id: string, subaccount: string, share: number): Promise<PaystackResponse<TransactionSplit>>;
    /**
     * Remove a subaccount from a transaction split
     *
     * @remarks
     *
     * For typescript users, you may experience inconsistencies in the returned data such as
     * the data returned doesn't match the method return type or the data returned has
     * more fields that are not showing up or flagged as errors. This is because no validation
     * is done to check if the actual returned data matches the return type. The returned data
     * is just cast as the return type. Also, the return types are based on the seen data as at
     * the time of implementation and are subject to errors and changes from paystack (e.g.,
     * paystack adding more fields, which makes the models incorrect). When faced with this issue
     * in development, you may cast the method return type as `any` and then cast is to a return
     * type that serves your purpose. Also, please create an issue for it at
     * https://github.com/gray-adeyi/paystack-sdk/issues so the issue is fixed in future releases.
     *
     * @param id - The split id
     * @param subaccount - This is the subaccount code
     *
     * @returns A promise that resolves to an object whose type is {@link PaystackResponse}.
     * The data property of the object is another object of type {@link TransactionSplit}
     */
    remove(id: string, subaccount: string): Promise<PaystackResponse<TransactionSplit>>;
}
//# sourceMappingURL=transactionSplit.d.ts.map