Billecta
Target Audience: Administrators, Integration Managers, Superusers
Payment Provider Billecta¶
This section describes the various fields and properties of the Billecta payment provider in more detail. The configuration is created under Security → Payment provider configurations.
Info and credentials¶
| Name | Description |
|---|---|
| Payment configuration name | A name for the configuration, e.g. "Billecta configuration" |
| Titles | The titles that may use this configuration |
| Api key | The username of the Billecta account that is used for all transactions between Billecta and Payway |
| Api secret | The password of that Billecta account |
| Api SecureToken | May be used instead of the api key and secret. Configured by the Payway team — contact support |
| Invoice creator id | The CreditorPublicId of the creditor used for this configuration. Found under Invoice sender in Billecta |
| Currency | The currency that is used for all purchases (EUR, SEK) |
Settings for Billecta¶
| Name | Description |
|---|---|
| Payment terms for new purchase (days) | Days the customer has to pay the first invoice, counted from the purchase. 1–365 |
| Invoice sent before due/renewal date (days) | Days before the renewal date that the renewal invoice is sent. 0–365, where 0 sends it on the renewal date |
| Credit period on renewal (days) | Days the customer has to pay the renewal invoice, counted from the day it is sent. 1–365. Leave it empty to use the advance notice above, which puts the due date on the renewal date. Required when the advance notice is 0 |
| Payment terms for monthly invoice on new purchase (days) | Days the customer has to pay a monthly subscription's first invoice. 1–14 |
| Monthly invoice sent before due/renewal date (days) | Days before the renewal date that a monthly invoice is sent. 0–14 |
| Credit period on renewal, monthly (days) | The same as the credit period above, for a monthly subscription. 1–14 |
| Grace period for unpaid delivery (days) | Days the subscription keeps being delivered past the due date before it is stopped. 0–365 |
| Invoice will be closed and credited after (days) | Days until the invoice will be closed and credited after it has expired. 1–365 |
| Send credit invoice to customer after the invoice has been written off | Sends the customer a credit invoice once the invoice has been written off |
| Information text on the invoice | Free text added to the invoice a few rows after the product description |
How the renewal dates are calculated¶
invoice date = renewal date − invoice sent before due/renewal date
due date = invoice date + credit period on renewal
period start = renewal date
The advance notice and the credit period are separate settings, because how far ahead a publisher invoices and how long it then gives the customer to pay are two different decisions. Leaving the credit period empty makes it equal to the advance notice, which is how renewals behaved before the field existed: the invoice falls due exactly on the renewal date.
Warning
Check the write-off period against the grace period. Write-off is measured from the due date, grace from the later of the period start and the due date. A credit period shorter than the advance notice puts the due date before the period start and the two drift apart, so an invoice can be written off and credited while the customer is formally still within grace. Keep the write-off period longer than (advance notice − credit period) + grace period.
Package-specific payment terms¶
The day fields above apply to every package on the titles this configuration covers. A single package can be given different terms — for example business customers invoiced on other terms than private ones — with a payment terms configuration. A package then takes all of its day fields from those terms rather than from this configuration.
Payment methods¶
Choose the payment methods that will be available as payment periods for packages and campaigns.