Excerpt |
---|
This method is creating a new payment with the intention to pay the whole outstanding amount of a specific bill. The method can be applied on a single billonly. The payment is created in a posted state |
Resource URL
Parameters
...
Name
...
Type
...
Description
...
token
...
String
...
The token retrieved from the login method
...
(semi-optional)
...
Accounts Receivable Identifier
...
Excerpt |
---|
This method is creating a new payment with the intention to pay the whole outstanding amount of a specific bill. The method can be applied on a single billonly. The payment is created in a posted state |
Resource URL
Parameters
Name | Type | Description | |||||||||||
token | String | The token retrieved from the login method | |||||||||||
accounts_receivable_identifier (semi-optional) | Accounts Receivable Identifier | The identifier of the accounts receivable in which the payment should be allocated to. The allowed accounts receivable identifier fields are the following:
| |||||||||||
wallet_identifier (semi-optional) | Wallet Identifier | The identifier of the wallet in which the payment should be allocated to. The allowed wallet identifier fields are the following:
Only the unconditional wallet funds can be used in order to pay off Bills
| |||||||||||
type_identifier (mandatory) | Financial Transaction Type Identifier | The financial transaction type of the payment. The allowed financial transaction type identifier field are the following:
| |||||||||||
category_identifier (semi-optional) | Wallet IdentifierFinancial transaction category identifier | The identifier of the wallet in which financial transaction category of the payment that should be allocated toreturned as a result. The allowed wallet financial transaction category identifier fields are the following: type
Only the unconditional wallet funds can be used in order to pay off Bills
| |||||||||||
payment_method_identifier (mandatory) | Financial Transaction Type IdentifierPayment method identifier | The financial transaction type payment method of the payment. The allowed financial transaction type identifier field allowed payment method identifier fields are the following:
| |||||||||||
categorybill_identifier (optionalmandatory) | Financial transaction category Bill identifier | The financial transaction category of the payment that should be returned as a resultinvoice to be paid. The allowed financial transaction category invoice identifier fields are the following:
| |||||||||||
paymentbill_number_methodcheck_identifierdigit (mandatory on conditions) Payment method identifier | Number | The payment method check digit of the payment. The allowed payment method identifier fields are the following: | V4:payment_method_identifier | V4:payment_method_identifier | bill_identifier (mandatory) | Bill identifier | The invoice to be paid. The allowed invoice identifier fields are the following:
| V4:bill_identifier | V4:bill_identifier | payment_codebill's number. Applicable and mandatory if the bill to be paid has such a check digit
Tip |
---|
Available from CRM.COM R14.0.0 |
accounts_receivable_check_digit
(mandatory on conditions)
The check digit of the bill's accounts receivable number. Applicable and mandatory if the bill to be paid has such a check digit
Tip |
---|
Available from CRM.COM R14.0.0 |
bill_amount_check_digit
(mandatory on conditions)
The payment code if the bill that will be paidcheck digit of the bill's accounts receivable number. Applicable and mandatory if the bill to be paid has a payment code and the payment code rules are enabled for the type of the payment being postedsuch a check digit
Tip |
---|
Available from CRM.COM R14.0.0 |
received_on
(optional)
received_by_user_identifier
(optional)
The user who actually received the payment. It defaults to the issued by user if not specified. The allowed user identifier fields are the following:
Include Page | ||||
---|---|---|---|---|
|
received_by_unit_identifier
(optional)
Include Page | ||||
---|---|---|---|---|
|
card_identifier
(mandatory on conditions)
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 | ||||
---|---|---|---|---|
|
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)
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 | ||||
---|---|---|---|---|
|
Tip |
---|
notes
(optional)
back_office_code
(optional)
A back office code for the payment. If specified then it should be unique
Tip |
---|
udf_string_1
(optional)
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
fields_set
(optional)
A list of fields that should be included in the results. If not specified then all the available fields will be returned
Tip |
---|
Restrictions
- It is mandatory to specify one of the semi-optional parameters. Only one of those parameters is allowed to be specified.
...