| | |
---|
action
(mandatory) | String | Defines if a new or existing payment preference will be used. In the case of a payment preference then it also defines if the existing payment preference should be updated or not. The supported values are the following: ADD, UPDATE, REMOVE |
accounts_receivable_payment_preference_identifier
(mandatory and applicable only on update or remove) | Accounts Receivable Payment Preference Identifier | The identifier of the accounts receivable payment preference to be updated. The allowed accounts receivable payment preference identifier fields are the following: Include Page |
---|
| accounts_receivable_payment_preference_identifier |
---|
| accounts_receivable_payment_preference_identifier |
---|
|
|
payment_preference_identifier
(mandatory and applicable only on add) | Payment Preference Identifier | The identifier of the payment preference to be updated on the related accounts receivable payment preference object. The allowed payment preference identifier fields are the following: Include Page |
---|
| payment_preference_identifier |
---|
| payment_preference_identifier |
---|
|
|
account_holder (optional) | String | The account holder of the retrieved payment preference |
is_default (mandatory) | Boolean | Defines if the payment preference is default or not. |
bank_account_number (optional) | String | The bank account number of the retrieved payment preference |
bank_account_type_identifier (optional) | Bank Account Type Identifier
| The identifier of the bank account type to be added on account payment preference object. The allowed bank account type identifier fields are the following: Include Page |
---|
| bank_account_type_identifier |
---|
| bank_account_type_identifier |
---|
|
|
bank_identifier (optional) | Bank Identifier
| The identifier of the bank to be added on account payment preference object. The allowed bank identifier fields are the following: Include Page |
---|
| bank_identifier |
---|
| bank_identifier |
---|
|
|
bank_branch_identifier (optional) | Bank Branch Identifier
| The identifier of the bank branch to be added on account payment preference object. The allowed bank branch identifier fields are the following: Include Page |
---|
| bank_branch_identifier |
---|
| bank_branch_identifier |
---|
|
|
notes (optional) | String | The notes to be added on account payment preference object. Tip |
---|
Available from CRM.COM R10.1.0 |
|
payment_medium_identifier (optional) | String | The payment medium identifier to be added on account payment preference object. Tip |
---|
Available from CRM.COM R11.0.0 |
|
payment_medium_type_identifier (optional) | Payment Medium Type Identifier | The payment medium type to be added on account payment preference object. The allowed payment medium type identifier fields are the following: Include Page |
---|
| payment_medium_type_identifier |
---|
| payment_medium_type_identifier |
---|
|
Tip |
---|
Available from CRM.COM R11.0.0 |
|
payment_medium_brand_identifier (optional) | Payment Medium Brand Identifier | The payment medium brand to be added on account payment preference object. The allowed payment medium brand identifier fields are the following: Include Page |
---|
| payment_medium_brand_identifier |
---|
| payment_medium_brand_identifier |
---|
|
Tip |
---|
Available from CRM.COM R11.0.0 |
|
use_for_recurring_payments (optional) | Boolean | Indicates if the specific accounts receivable payment preference will be used to automatically pay any unsettled billes allocated to the related accounts receivable |
business_identifier_code (optional) | String | The business identifier code that identifies the bank , which should be consisted of (supports 8 or 11 alphanumeric characters) Applicable only for payment preferences of type DIRECT DEBIT or CUSTOM, as specified through the configuration Tip |
---|
Available from CRM.COM R13.1.0 |
|
unique_mandate_reference (optional) | Number | The unique reference, which identifies a mandate that was signed by a Debtor for any given Creditor (supports up to 35 alphanumeric characters) Applicable only for payment preferences of type DIRECT DEBIT or CUSTOM, as specified through the configuration Tip |
---|
Available from CRM.COM R13.1.0 |
|
mandate_signing_date (optional) | Date | The date that the mandate was signed Applicable only for payment preferences of type DIRECT DEBIT or CUSTOM, as specified through the configuration Tip |
---|
Available from CRM.COM R13.1.0 |
|
mandate_termination_date (optional) | Date | The date that the mandate will be terminated. No payments should be send after that date (inclusive) Applicable only for payment preferences of type DIRECT DEBIT or CUSTOM, as specified through the configuration Tip |
---|
Available from CRM.COM R13.1.0 |
|
cards_set (mandatory on add)
| Set of payment gateway cards objects | The cards that are related with the accounts receivable payment preference, in case the payment preference is related with a payment gateway such as Stripe. This information is applicable only if the payment preference is related with a payment gateway. In that case it is mandatory to specify at least one card, which also needs to be set as the default card Include Page |
---|
| Web API - Updating Sets |
---|
| Web API - Updating Sets |
---|
|
|