POST accounts_receivable/update

(mandatory)

Defines if a new or existing address will be used. In the case of an existing address then it also defines if the existing address should be updated or not. The supported values are the following:

NEW, EXISTING, EXISTINGUPDATED

(mandatory on conditions)

The contact information address that should be set as the billing address address. This is applicable and mandatory only if the action is set to EXISTING or EXISTINGUPDATED. The supported options are the following:

HOME, BUSINESS, POBOX, CUSTOM1, CUSTOM2, CUSTOM3, CUSTOM4, CUSTOM5

address

(mandatory on conditions)

wallet_balance_threshold

(mandatory)

Number

top_up_amount

(mandatory)

Number

The amount that will top up the wallet balance

frequency

(mandatory)

Number

The minimum period (in days) between wallet top ups

product_conditions_set

(optional)

A set of products that will be allowed to consume the specified top up amount

If no records are specified in the set then nothing will be updated. To remove a record use action "remove". To add a record use action "add". Different actions can be used within the same set. For example:

"set": [
	   		{
            	"action": "remove",
            	...........
        	},
			{
            	"action": "add",
            	...........
			}
		]

(mandatory)

Defines if a new or existing presentment preference will be used. In the case of a presentment preference then it also defines if the existing presentment preference should be updated or not. The supported values are the following:

ADD, UPDATE, REMOVE

accounts_receivable_presentment_preference_identifier

(mandatory and applicable only on update or remove)

 The identifier of the accounts receivable presentment preference that will be updated. The allowed accounts receivable presentment preference identifier fields are the following:

(mandatory and applicable only on add)

Presentment Preference Identifier  

The identifier of the presentment preference related with the accounts receivable presentment preference that will be updated. The allowed presentment preference identifier fields are the following:

state

(optional and applicable only on add or update)

email

(mandatory and applicable only on add or update)

The email that should be related with the presentment preference. The email is mandatory and applicable only if the specified presentment preference is of type Email

phone

(mandatory  and applicable only on add or update)

The phone that should be related with the presentment preference. The phone is mandatory and applicable only if the specified presentment preference is of type SMS

(mandatory)

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

(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:

(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:

account_holder

(optional)

String

The account holder of the retrieved payment preference

is_default

(mandatory)

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:

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:

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:

notes

(optional)

The notes to be added on account payment preference object.

payment_medium_identifier

(optional)

The payment medium identifier to be added on account payment preference object.

payment_medium_type_identifier

(optional)

The payment medium type to be added on account payment preference object. The allowed payment medium type identifier fields are the following:

payment_medium_brand_identifier

(optional)

The payment medium brand to be added on account payment preference object. The allowed payment medium brand identifier fields are the following:

use_for_recurring_payments

(optional)

Indicates if the specific Accounts Receivable Payment Preference will be used to automatically pay any unsettled bills allocated to the related accounts receivable. Applicable only if the Payment Preference is related to a Payment Gateway

 opt_in_for_subscriptions

(optional)

Indicates if the specific Accounts Receivable Payment Preference will be used to automatically pay any unsettled bills allocated to the related accounts receivable, related to its subscriptions. Applicable only if the Payment Preference is related to a Payment Gateway

 opt_in_for_purchases

(optional)

Indicates if the specific Accounts Receivable Payment Preference will be used to automatically pay any unsettled bills allocated to the related accounts receivable, related to purchases. Applicable only if the Payment Preference is related to a Payment Gateway

iban

(optional)

The international bank account number

Applicable only for payment preferences of type DIRECT_DEBIT, GENERIC_PAYMENT_GATEWAY, OTHER, CUSTOM_1, CUSTOM_2, CUSTOM_3, CUSTOM_4, CUSTOM_5, as specified through the configuration

business_identifier_code

(optional)

The business identifier code that identifies the bank

Applicable only for payment preferences of type DIRECT_DEBIT, GENERIC_PAYMENT_GATEWAY, OTHER, CUSTOM_1, CUSTOM_2, CUSTOM_3, CUSTOM_4, CUSTOM_5, as specified through the configuration

unique_mandate_reference

(optional)

The unique reference, which identifies a mandate that was signed by a Debtor for any given Creditor

Applicable only for payment preferences of type DIRECT_DEBIT, GENERIC_PAYMENT_GATEWAY, OTHER, CUSTOM_1, CUSTOM_2, CUSTOM_3, CUSTOM_4, CUSTOM_5, as specified through the configuration

mandate_signing_date

(optional)

The date that the mandate was signed

Applicable only for payment preferences of type DIRECT_DEBIT, GENERIC_PAYMENT_GATEWAY, OTHER, CUSTOM_1, CUSTOM_2, CUSTOM_3, CUSTOM_4, CUSTOM_5, as specified through the configuration

mandate_termination_date

(optional)

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, GENERIC_PAYMENT_GATEWAY, OTHER, CUSTOM_1, CUSTOM_2, CUSTOM_3, CUSTOM_4, CUSTOM_5, as specified through the configuration

gateway_payment_method_token

(optional)

The token of the payment gateway payment method that will be registered (defines payment methods other than cards)

cards_set

(mandatory on add)

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

"set": [
	   		{
            	"action": "update",
            	...........
        	},
			{
            	"action": "remove",
            	...........
			},
			{
            	"action": "add",
            	...........
			}
		]