AddStopPayment module
Add stop payment
- class q2_sdk.hq.hq_api.wedge_online_banking.AddStopPayment.ParamsObj(logger, hq_credentials, process_date, originating_account_id, transaction_amount, currency_code, description, check_number, payee_name, check_date)[source]
Bases:
WedgeOnlineBankingParamsObj
Parameters definition for AddStopPayment
- Parameters:
logger (
TypeAliasType
) – Reference to calling request’s logger (self.logger in your extension)hq_credentials (
HqCredentials
) – HqCredentials instance with an hq_url and auth_tokenprocess_date (
str
) – ex. 1980-10-23. Some HQ endpoints require a timestamp as well (1980-10-23T00:00:00)originating_account_id (
int
) – Q2_HostAccount.HostAccountIDtransaction_amount (
float
) – ex. 2.43currency_code (
str
) – Q2_CurrencyCode.CurrencyCode. The currency to use for a transaction. This will almost always be “USD”description (
str
) – Free form textcheck_number (
str
)payee_name (
str
)check_date (
str
)
- async q2_sdk.hq.hq_api.wedge_online_banking.AddStopPayment.execute(params_obj, use_json=False, **kwargs)[source]
This is the default way to submit the request to HQ. In theory, both json and soap payloads are equally accepted by HQ, though several variables may affect that (HQ version, Q2SDK implementation bugs, etc). This should not affect anything about the way your code deals with the data. In fact, the only difference to consuming extensions is the logging. Basically, call this with default parameters unless you find a compelling reason not to.
- Parameters:
params_obj (
ParamsObj
) – Object containing everything necessary to call this HQ endpointuse_json – If True, will call HQ’s .ashx (json) endpoint instead of .asmx (soap)
- Return type:
- async q2_sdk.hq.hq_api.wedge_online_banking.AddStopPayment.get_soap(params_obj, **kwargs)[source]
Deprecated. Please use execute instead
- Return type: