/api/PreauthAsk AIpost https://example.com/api/PreauthBody ParamspspSettingsIdstring | nullThe identifier of PSP settings to identify a PSP module. Mandatory. Not used now, since part of not ended integration flow with billwerk.transactionIdstring | nullThe transaction identifier from billwerk side. Format: {yyyyMMdd}-{ObjectId} Mandatory.requestedAmountdoublePreauth requested amount. Mandatory. Not negative number.currencystring | nullThe currency of preauth. Mandatory. ISO-4217 format.webhookTargetstring | nullThe notification URL from billwerk side. Mandatory.paymentMeansReferenceobjectRepresents the payment means ref data. It include needed info for initial preauth request.paymentMeansReference objecttransactionInvoiceReferenceTextstring | nullThe reference text of invoice linked to preauth transaction. Optional, experimental one! Can be changed/replaced in future! Includes linked invoice reference code, description and unique reference of transaction. Mandatory.transactionReferenceTextstring | nullThe reference text for transaction. Includes billwerk preauth transaction id, description and unique reference of transaction. Mandatory.payerDataobjectRepresents a payer datapayerData objectorderDataobjectRepresents the order related data.orderData objectagreementIdstring | nullId which specify agreement between 3-rd party integration and billwerk according payment actions, which initiated by billwerk for specific customer and supported by 3-rd party integration. Mandatory.migrationTokenstring | nullThe data required for migration via technical bearer Used to identify existing agreement/customer on PSP side to migrate contract date to billwerk. OptionalisInitialbooleanIndicate, if preauth transaction initial or not. Mandatory. WARNING - can be replaced with separate endpoints for initial and non-initial preauth calls.truetruefalseResponse 200SuccessUpdated 8 months ago