- Created by George Rossides (Unlicensed), last modified on Aug 04, 2016
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 5 Next »
Name | Type | Description | |||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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:
| |||||||||||||||||||||||||||
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:
| |||||||||||||||||||||||||||
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:
| |||||||||||||||||||||||||||
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:
| |||||||||||||||||||||||||||
payment_medium_identifier (optional) | String | The payment medium identifier to be added on account payment preference object. Available from CRM.COM R11.0.0 | |||||||||||||||||||||||||||
payment_medium_type (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:
Available from CRM.COM R11.0.0 | |||||||||||||||||||||||||||
payment_medium_brand (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:
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 Available from CRM.COM R5.0.0 | |||||||||||||||||||||||||||
(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
If no records are specified in the set then nothing will be updated. To update a record use "action" : "update". 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": "update", ........... }, { "action": "remove", ........... }, { "action": "add", ........... } ]
Available from CRM.COM R5.0.0 |
Referred Objects Response Data
Name | Type | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
action (mandatory) | String | Defines if a new or existing payment gateway card will be added, updated or removed. The supported values are the following: ADD, UPDATE, REMOVE | ||||||||||||
payment_gateway_card_identifier (mandatory and applicable only on update or remove) | Payment Gateway Card Identifier | The identifier of the payment gateway card that will be updated. The allowed payment gateway card identifier fields are the following:
The retrieved cards are always filtered based on their related accounts receivable payment preference and not across all cards | ||||||||||||
number (semi-optional and applicable only on add) | Number | The card's number, which should be a 16 digits number. This information is applicable only on adding a new card For releases prior CRM.COM R14.2.0, this parameter is mandatory | ||||||||||||
last_digits (semi-optional and applicable only on add) | String | The card last 4 digits Available from CRM.COM R14.2.0 | ||||||||||||
expiration_month (mandatory on add, optional only on update) | Number | The card's expiration month, which can be from 1 to 12 | ||||||||||||
expiration_year (mandatory on add, optional only on update) | Number | The card's expiration year which should be a 4 digits number | ||||||||||||
card_security_code (optional, applicable only on add) | Number | The security code of the card, which should be a 3 digits number. This information is applicable only on adding a new card. | ||||||||||||
card_holder_name (optional, applicable only on add and update) | String | The card holders name, as provided during the registration of the card | ||||||||||||
brand (mandatory on conditions, applicable only on add) | String | The card's brand, as provided by the payment gateway provider. The supported brands by the payment gateway are the following:
This attribute is mandatory for Payeezy Payment Gateway Available from CRM.COM R14.3.0 | ||||||||||||
address_line_1 (optional, applicable only on add and update) | String | Information related with the card's billing address | ||||||||||||
address_line_2 (optional, applicable only on add and update) | String | Information related with the card's billing address | ||||||||||||
address_city (optional, applicable only on add and update) | String | Information related with the card's billing address | ||||||||||||
address_zip (optional, applicable on add and update) | String | Information related with the card's billing address | ||||||||||||
address_state (optional, applicable only on add and update) | String | Information related with the card's billing address | ||||||||||||
address_country (optional, applicable only on add and update) | String | Information related with the card's billing address | ||||||||||||
card_token (optional, applicable only on add and update) | String | The token of the card that will be registered Available from CRM.COM R14.2.0 | ||||||||||||
consumer_token (optional, applicable only on add and update) | String | The consumer token of the card that will be registered Available from CRM.COM R14.26.0 | ||||||||||||
default (optional, applicable only on add and update) | Boolean | It defines the default payment gateway card that should be used while automatically creating payments against that specific accounts receivable. The default card is also set on payments done using the specific payment preference, although the user can modify this information, by selecting an additional card. Note that on setting a card as the default, the previous default card is automatically replaced |
- No labels