Placeholders for configuring payment methods

The following placeholders can be used for configuring payment methods (see Creating a payment method).

PlaceholderDescription

payment.payment_method

The payment method name
payment.account_idThe ID of an account linked to the payment
payment.account_nameThe full name of an account linked to the payment
payment.account_type_keyThe account type key of an account linked to the payment
payment.account_custom_attributes['attribute_key']The value of an additional attribute with the given key (see Creating an attribute) of an account linked to the payment
payment.account_addressThe full address of an account linked to the payment. Autogenerated from the address information of the account (see Creating an account). Example: 143246, Germany, Hesse region, Dreieich city, Hainer str., building 3, office 5
payment.account_emailThe email of an account linked to the payment
payment.account_phoneThe phone number of an account linked to the payment
payment.account_countryThe country code of an account linked to the payment
payment.account_country_nameThe country name of an account linked to the payment
payment.account_regionThe region of an account linked to the payment
payment.account_cityThe city of an account linked to the payment
payment.account_zipThe zip of an account linked to the payment
payment.account_streetThe street of an account linked to the payment
payment.account_buildingThe building of an account linked to the payment

payment.id

The payment ID

payment.document_id

The payment document number
payment.document_numberThe payment number in the payment document
payment.totalThe payment total
payment.total_in_wordsThe payment total in letters
payment.status

  • Waiting for payment (waiting_for_payment — in the API methods) — the initial status of a new payment. A payment is created and not yet completed.
  • Expired — a payment is not completed before the due date.
  • Cancelled — a payment is cancelled.
  • Receipt creating (receipt_creating) — a manager manually prepares a receipt (see Processing a payment that requires manual receipt creation).
  • Receipt sent (receipt_sent) —  a manager sent a manually prepared receipt to a customer.

  • Processing — a temporary status while a payment on the payment gateway side is processed. In the Processing status, all operations for a payment are not available.
  • Completed — a payment is processed (a customer paid for a payment).
  • Paid from balance (paid_from_balance) — a customer paid for a payment using the account balance.

payment.commentThe payment comment
payment.ordersInformation about orders linked to the payment (semicolon-separated list)
payment.order_chargesThe list of the charges linked to the payment (separated by ";"): description, quantity, unit_price, unit_price_without_tax, discount_amount, discounted_unit_price_without_tax, amount_without_tax, period, tax_percent, amount, discount_ids
payment.order_charges.sizeThe number of charges in a PDF receipt
payment.order_charges[].has_taxesBool; indicates whether a payment item has taxes
payment.order_charges[].taxes_amountThe sum of all taxes in a payment
payment.order_charges[].taxes[]The array of taxes included in a payment
payment.order_charges[].taxes[].idThe ID of a tax
payment.order_charges[].taxes[].nameThe name of a tax
payment.order_charges[].taxes[].codeThe code of a tax
payment.order_charges[].taxes[].amountThe amount of a tax
payment.grouped_order_charges

The list of the grouped charges linked to the payment (separated by ";" parameters are set for the first charge in a group if not specified otherwise): id; name; description; unit_price (price); amount (specified as the total amount for a group); duration (period); discount_ids; discount_amount (specified as the total amount for a group); quantity (specified as the total amount for a group); operate_from; operate_to; type; plan_id; plan_name; plan_resource_id; unit_price_without_tax; discounted_unit_price_without_tax; amount_without_tax (specified as the total amount for a group); unit_price_with_discount; tax_percent.

Example for displaying as a table:

{% for charge in payment.grouped_order_charges %} <tr>
  <td>{{ charge.plan_id }}</td>
  <td>{{ charge.plan_name }}</td>
</tr>
{% endfor %}

Charges are grouped if have the following identical parameters:

  • reseller_id
  • account_id
  • subscription_id
  • resource_id
  • operate_from
  • operate_to
  • duration
  • unit_price
  • status
  • type
  • taxes_amount
  • discount_id
  • original_amount_currency
  • currency_rate
  • currency_unit
payment.grouped_order_charges.sizeThe number of grouped charges in a PDF receipt
payment.created_atThe date and time when the payment is created
payment.provisioning_itemsInformation about resources linked to the payment
payment.positive_provisioning_itemsInformation about resources linked to the payment and with the resource amount greater than 0
payment.topup?The indicator of a top-up payment
payment.topup_sumThe top-up amount
payment.automatically_generated?The indicator of a payment created automatically by the platform
payment.invoicesInformation about Invoices linked to the payment
payment.panel_linkA link to the payment in the Customer Control Panel
payment.downloadableThe indicator of the availability of a downloadable receipt for the payment
payment.receipt_urlThe receipt download link for the payment
payment.purposeThe purpose of the top-up payment (see Creating a payment manually)
payment.due_date

The due date for the payment. Depending on the payment mode:

  • Prepay — the date is calculated considering the type of a linked order. For joined payments, the earliest date among the linked orders is selected.

    Order typeThe due date
    Sales orderThe order expiration date
    Change order
    Switch plan order
    Prolong order
    • If an order is created before the Paid to date of a subscription — the Paid to date of a subscription.
    • If an order is created after the Paid to date of a subscription — the subscription expiration date.

    Setting the Paid to date for different subscriptions is described in Prolonging a subscription

    Renewal order
    • If an order is created before the subscription expiration date — the earliest date among the subscription expiration date and order expiration date.
    • If an order is created after the subscription expiration date — the order expiration date.
  • Postpay — the due date of the payment.
payment.external_totalThe amount of a third-party invoice, if specified (see Managing invoices for the Postpay model by a third-party ERP system). For a PDF template only
payment.external_currencyThe ISO code of the currency of a third-party invoice, if specified (see Managing invoices for the Postpay model by a third-party ERP system). For a PDF template only
payment.pdf_urlUsed in the instructions template for a payment method based on the CheckCash plugin: a link to download a PDF receipt generated by the platform using a template from PDF Template (in Liquid format) (see Creating a payment method)
payment.external_file_url

Used in the instructions template for a payment method based on the CheckCash plugin:

  • A link to download a PDF receipt generated by the platform using a template from PDF Template (in Liquid format) (see Creating a payment method) — in the following cases:
    • For a prepaid payment.
    • For a postpaid payment when the platform itself manages postpaid invoices.
    • For a postpaid payment when external management of postpaid invoices is used, but a third-party ERP system did not attach a third-party invoice to a payment.
  • A link to download a third-party invoice attached to a postpaid payment by a third-party ERP system in the form of a link or file when external management of postpaid invoices is used.

See also Managing invoices for the Postpay model by a third-party ERP system.