Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Tip

Available from CRM.COM R9.1.0

...

Name

Type

Description

token

String

The token retrieved from the login method

payment_identifier

(mandatory)

Payment Identifier  

The identifier of the payment that should be updated. Only payments in draft state can be specified.The allowed payment identifier fields are the following:

Include Page
V4:payment_identifier
V4:payment_identifier

accounts_receivable_identifier

(optional)

Accounts receivable identifier

The identifier of the payment's updated accounts receivable. The allowed accounts receivable identifier fields are the following:

Include Page
V4:accounts_receivable_identifier
V4:accounts_receivable_identifier

Tip
From CRM.COM R14.0.0 and onwards, if the wallet_identifier parameter is set, then this parameter cannot be defined


wallet_identifier

(optional)

Wallet Identifier

The identifier of the wallet in which the payment should be allocated to. The allowed wallet identifier fields are the following:

Include Page
V4:wallet_identifier
V4:wallet_identifier

In addition the following conditions apply:

  • If the payment using Wallet funds functionality is not enabled through the Wallet Definition, then this parameter is not applicable
  • If the accounts_receivable_identifier parameter is set, then this parameter cannot be defined
Tip

Available from CRM.COM R14.0.0


type_identifier

(optional)

Financial transaction type identifier

The updated financial transaction type of the payment. Only financial transaction types with Payment classification can be specified. The allowed financial transaction type identifier fields are the following:

Include Page
V4:financial_transaction_type_identifier
V4:financial_transaction_type_identifier

Tip
From CRM.COM R14.0.0 and onwards, if the wallet_identifier parameter is set, then this parameter cannot include Payment Gateways


category_identifier

(optional)

Financial transaction category identifier

The financial transaction category of the payment. The allowed financial transaction category identifier fields are the following:

Include Page
V4:financial_transaction_category_identifier
V4:financial_transaction_category_identifier

payment_method_identifier

(optional)

Payment Method identifier

The updated Payment Method of the payment. The allowed payment method identifier fields are the following:

Include Page
V4:payment_method_identifier
V4:payment_method_identifier

card_identifier

(mandatory on conditions)

Payment Gateway Card Identifier

The card that will be charged for the amount specified on the payment, by the related payment gateway provider. The allowed payment gateway card identifier fields are the following:

Include Page
V4:payment_gateway_card_identifier
V4:payment_gateway_card_identifier

The card is applicable and mandatory if the specified payment method is linked with a payment gateway system. Note that the retrieved cards are filtered based on the cards owned by the specified accounts receivable owner

accounts_receivable_payment_preference_identifier

(mandatory on conditions)

Accounts Receivable Payment Preference Identifier

The accounts receivable payment preferences that will be used by generic payment gateways to process the payment. The specified accounts receivable payment preferences should belong to the specified accounts receivable. This information is applicable and mandatory only if the payment will be processed by a generic payment gateway, as denoted by the selected payment method. The allowed accounts receivable payment preference identifier fields are the following:

Include Page
V4:accounts_receivable_payment_preference_identifier
V4:accounts_receivable_payment_preference_identifier

Tip

Available from CRM.COM R11.0.0

From CRM.COM R14.0.0 and onwards, this parameter is mandatory only if the accounts_receivable_identifier parameter is specified. If the wallet_identifier parameter is specified then this information is not applicable


received_by_user_identifier

(optional)

User identifier

The user who actually received the payment. The allowed user identifier fields are the following:

Include Page
V4:user_identifier
V4:user_identifier

received_by_unit_identifier

(optional)

Unit identifier
The unit who actually received the payment. The allowed unit identifier fields are the following:

Include Page
V4:unit_identifier
V4:unit_identifier

Tip

Deprecated from CRM.COM R18.0.0


received_by_business_unit_identifier

(optional)

Business Unit identifier
The business unit who actually received the payment. The allowed business unit identifier fields are the following:

Include Page
V4:business_unit_identifier
V4:business_unit_identifier

Tip

Available from CRM.COM R18.0.0


received_on

(optional)

DateThe date that the payment was received. It defaults to the issued date if not specified

payment_amount

(optional)

NumberThe Payment's updated amount

intended_currency_identifier

(optional)

Currency Identifier

The currency that the user was intended to use for the payment. If specified then it is validated against the currency of the specified accounts receivable and if they don't match then an error is throw. Note that the intended currency is not saved within CRM.COM; it is just used for validation purposes. The allowed currency identifier fields are the following:

Include Page
V4:currency_identifier
V4:currency_identifier

Tip

Available from CRM.COM R11.0.0


notes

(optional)

StringShared notes for the payment

back_office_code

(optional)

String

A back office code for the payment. If specified then it should be unique


job_identifier

(optional)

Job Identifier

The job for which the payment was done for. The allowed job identifier fields are the following:

Include Page
V4:job_identifier
V4:job_identifier

Tip

Available from CRM.COM R14.4.0


posted_on

(optional)

Date

The posting date of the financial transaction which is before or equal to the current date and not included in already closed accounting periods. If not specified then the current date is applied. 

Tip

Available from CRM.COM R14.10.0


udf_string_1

(optional)

String

User Defined Field of type String

udf_string_2

(optional)

String

User Defined Field of type String

udf_string_3

(optional)

String

User Defined Field of type String

udf_string_4

(optional)

String

User Defined Field of type String

udf_string_5

(optional)

String

User Defined Field of type String

udf_string_6

(optional)

String

User Defined Field of type String

udf_string_7

(optional)

String

User Defined Field of type String

udf_string_8

(optional)

String

User Defined Field of type String

udf_float_1

(optional)

Float

User Defined Field of type Float

udf_float_2

(optional)

Float

User Defined Field of type Float

udf_float_3

(optional)

Float

User Defined Field of type Float

udf_float_4

(optional)

Float

User Defined Field of type Float

udf_date_1

(optional)

Date

User Defined Field of type Date

udf_date_2

(optional)

Date

User Defined Field of type Date

udf_date_3

(optional)

Date

User Defined Field of type Date

udf_date_4

(optional)

Date

User Defined Field of type Date

invoices_to_pay_set

(optional)

Set of invoice objects

The invoices that are intended to be paid

Include Page
V4:Web API - Updating Sets
V4:Web API - Updating Sets

bills_to_pay_set

(optional)

Set of bill objects

The bills that are intended to be paid

Include Page
V4:Web API - Updating Sets
V4:Web API - Updating Sets

products_to_pay_set

(optional)

Set of product objects

The service products that are intended to be paid through this payment. Applicable only if the account owner owns an effective wallet and the payment is also included as a wallet credit cause in active Wallet definititions.

Include Page
V4:Web API - Updating Sets
V4:Web API - Updating Sets

Tip

Available from CRM.COM R12.0.0


fields_set

(optional)

List of Strings, comma separated 

A list of fields that should be included in the results. If not specified then all the available fields will be returned

...