Payment methods allow in xentral, on the one hand, the setting of certain payment types in documents, which then with their typesetting a specific payment type (e.g. type prepayment > prepayment payment type, type invoice > expiry of invoice days for dunning, Type Direct debit > appears in the direct debit collection). On the other hand, different payment providers can be connected via API using modules (e.g. Klarna, Payone, PayPalPlus, etc.).
By default, the most common payment methods are already pre-created in xentral. Should you not find a payment method in the list or need one twice, you can create your own new payment methods. Each payment method can be assigned to a module (e.g. Klarna, Payone, PayPalPlus, etc.). xentral payment methods do not need an external module here. If additional/different payment methods are needed than already offered, they can be added under Administration > Settings > Payment methods > Overview > NEW.
xentral ships with default payment methods pre-created. These can be used directly and inserted into documents. The mere payment method (without API connection to a payment provider e.g. Klarna) thus provides first of all the possibility to insert the payment method in the document and to print it as well as a specific payment behavior for the dunning process and statistical quantity evaluations of the document overviews according to payment methods.
If the API connection is to be used for an external payment provider the settings fields must also be filled in with the payment provider portal access data. Thus, the payment providers are directly connected to xentral and can generate payment information for xentral and status feedback. (e.g. Klarna).
Practical info example Klarna
A module such as Klarna is at the same time a connection from xentral to the Klarna payment provider API. Through this, feedback is sent from xentral with triggers or process starters to Klarna. During the order import from the store, the payment information from Klarna is also sent to xentral. Klarna is delivered to xentral and printed on the receipt so that the customer can transfer the money correctly.
Practical info example direct debit
A xentral internal module such as Direct Debit has only xentral internal links. For example, a new payment method must have the properties of Direct Debit if this payment method is also proposed in the interfaces for direct debit collection and has identical behavior to the default payment type Direct Debit in xentral. In this way, it is possible to get payment methods like Invoice and the related dunning algorithms to be saved.
Practical info store mapping
It is possible to edit these preset payment methods. Please note that the type of payment method that may be used in mappings for online stores is used in the xentral standard. E.g. the payment method Prepayment will be with the same type name prepayment for Shopware is used in the mapping of the Shopware payment method Prepayment as a counterpart. I.e. an order, which gets the payment method prepayment from Shopware, will be mapped to the payment method prepayment in xentral. Payment methods, which are available in the store, but not in xentral, are usually created during the store import. This newly created payment method therefore needs a field description in xentral and a field description from the online shop/e-commerce connection. Please check and if necessary, set correctly during the connection and test run of a store, the payment mapping in the respective store interface. The payment mapping in combination with stores can be found here .
Short facts about the payment methods:
-
Preset payment methods can be directly inserted into vouchers immediately
-
Payment methods and texts can be edited.
Note
Note the mappings, if online stores are present or other imports/exports take place
-
Payment methods can be translated into other languages via the globe icon and translation module
-
Optional: payment methods can be assigned to projects (be careful about visibility: the user will only see the payment method if he has received the project in the assigned address or ALL projects as a Role)
-
Never duplicate payment methods and their type names. Each payment method and its type must be unique
-
New payment methods can be created arbitrarily and any module and an arbitrary behavior be deposited (applies of course also for existing payment methods)
-
Payment methods can be deactivated or deleted. Deactivation is recommended if it is not yet clear whether the settings will be needed again later on or for test runs. The default payment methods in xentral should NEVER be deleted
The following payment methods are available (list includes special modules):
Note
The type must be entered exactly as written in the table or listed below, e.g., you need to write the type completely in lowercase letters. Otherwise the entry will be listed twice, once with its designation and once with its type, when selecting a payment method in a document.
-
kreditkarte → Credit card
-
rechnung → Invoice
-
nachnahme → Cash on delivery
-
vorkasse → Prepayment
-
eckarte → EC card payment
-
bar → Cash payment
-
paypal → PayPal
-
sofortueberweisung → Instant bank transfer
-
lastschrift → Direct debit
-
ratenzahlung → Installment
-
amazon → Amazon Payments
-
amazon_bestellung → Amazon order
-
billsafe → Billsafe
Payment methods can be accessed in xentral here and edited if necessary:
Administration > Settings > Payment methods
New payment methods can be added to the default ones (special Payment methods, mapping for online stores, etc.). To create a new payment method you navigate to:
Administration > Settings > Payment methods > Overview > NEW > Select payment method
Enter the data in the fields and save the page. The field explanations and how these are to be filled, you find with the respective payment method above in the table (link to the respective payment method). The new payment method can now be used in xentral.
Important
Avoid duplications to already existing payment methods in name and type. A module can also be used multiple times.
Practical info:
-
The name/description is free (at best a short word or short Expression, no complete sentences!). This textual designation appears in the software interface (selection of the payment method in the document). These descriptions of the payment methods can also be translated for the other document languages (gray globe)
-
The type of payment method is fixed (xentral type/field setting > Shops, payment provider interface) or freely selectable (no mapping necessary, the payment method is only needed for information purposes/variable on the document is required)
Example:
-
The payment methods can be set arbitrarily (type), as long as there is no connection for this payment method to an interface
-
If a payment method refers to a payment method from an online store, then the type is fixed (field name central) setting in the store interface
-
If a payment method refers to a payment provider interface (e.g. Klarna), the correct field name (type) and the appropriate module must be used. Field designations overview see store interface
If the desired payment method is not available, you can use Custom and +NEW to create a completely custom payment method. Detailed information on this can be found here .
The following fields must be filled in:
-
Designation: Freely selectable designation. This is displayed in the selection drop-down of the payment methods in the document
-
Type: Must be unique for each payment method and may not contain spaces and special characters. The type is used for mapping in stores
-
Module: The selection of the module is important for special payment methods like Klarna or Paypal Plus. The change of the module resets the previous Settings back. For a custom payment method without API module leave the one on the drop-down on the empty entry
-
Text on voucher: This text will be printed on the voucher below the article table output if the payment method was selected in the document
-
Project: Possibility to restrict the payment method to a project. → here counts the document project
-
Autom. paid (invoice): Sets payment status of an invoice to 'paid'. This setting behaves as if an invoice would be manually set to paid
-
Auto paid (liability): Sets payment status of a liability to 'paid' and moves it to the 'paid' and moves it to the payables archive. This setting behaves as if a payable were manually set to paid
-
Behavior like: Invoice, prepayment, direct debit. Sets the behavior of a newly created payment method as for direct debit or invoice (eg: dunning behavior). Influences e.g. the discount fields in the document - with behavior invoice one has more fields to choose from than prepayment/direct debit
-
Active: Only active payment types are displayed in the document
Note
For orders imported via a store platform. The orders can be marked as paid in advance.
The texts for the payment methods can also be output differently with IF blocks per document:
{IF}{BELEGART}="Offer"{THEN}Payment in advance{ELSE}{ENDIF}
{IF}{BELEGART}="Order"{THEN}Payment in advance 2{ELSE}{ENDIF}
{IF}{BELEGART}="Invoice"{THEN}Paid in advance{ELSE}{ENDIF}
{IF}{BELEGART}="Credit note"{THEN}Reimbursement by bank transfer if already paid in advance{ELSE}{ENDIF}
A payment method can be inserted directly into a document. To do this, click on the document and select the payment method in the drop-down below the free text. + Save. For payment methods with extended fields you will find these in the box to the right of the payment method, e.g. payment term, cash discount, cash discount date etc.
Master data > Addresses
A payment method can be inserted directly into an address. To do this, click on the address and select the payment method in the drop-down + save. For some payment methods, you will find extended fields e.g. payment date, discount, discount days, etc. The payment method is adjustable for customers as well as for suppliers.
The payment methods behave in a certain way with the customer addresses:
-
If you have set a payment method in a customer address and create a new order from this address, then the set payment method of the customer address will be passed through
-
If you set a payment method in the project and an existing order (Change project), then the payment method from the project will reload and not keep the payment method from the customer address
Administration > Settings > System > Basic settings > Tax/currency.
A payment method can be set as the default payment method in the basic settings. If a customer does not have a default payment method this is used as default when creating a document.