Billwerk+ Transform automates not only recurring invoices but also regular payments. Billwerk+ Transform has integrated various payment service providers (PSP - Payment Service Provider). With this integration, billwerk not only triggers payments automatically, but also receives information about chargebacks or refunds if the payment providers support this.

You configure the payment provider(s) of your choice in your Billwerk+ Transform account, and the corresponding means of payment are already available to you. Details on the configuration of the payment providers can be found in the related articles in our Help Center.

Payment transaction

The payment transaction contains all data and the status history of an individual payment transaction with a payment service provider. The attributes are:

• Amount,
• Status history,
• Current status,
• Time of the last status change,
• Trigger of the transaction,
• Specific data of the payment provider

If a payment is captured manually without a payment service provider being involved, there is an entry in the Contract ledger for this payment, but no payment transaction.

Transaction Example:

{
    "InvoiceReferenceCode":"XFHNJ-LZHHL-GFCBS",
    "InvoiceId":"5b960ddd88472d07fc704bf9",
    "Id":"5b960e2a88472c05603cdb22",
    "PaymentProvider":"FakeProvider",
    "PaymentProviderRole":"Debit",
    "Trigger":"Signup",
    "CustomerId":"5b960dd488472d07fc704bdd",
    "CustomerName":"Ehrlich, Alyssa",
    "ContractId":"5b960dd488472d07fc704bde",
    "ProviderTransactionId":"8b47fb14-fef7-4250-b4ad-9784d74da9c7",
    "StatusHistory":[
        {
            "Status":"InProgress",
            "Timestamp":"2018-09-10T06:24:42.9910000Z",
            "Amount":89.25,
            "HttpCode":0,
            "Preauth":false
        },
        {
            "Status":"Succeeded",
            "Timestamp":"2018-09-10T06:24:44.9940000Z",
            "Amount":89.25,
            "HttpCode":0,
            "Preauth":false
        }
    ],
    "Status":{
            "Status":"Succeeded",
            "Timestamp":"2018-09-10T06:24:44.9940000Z",
            "Amount":89.25,
            "HttpCode":0,
            "Preauth":false
        },
        "Amount":89.25,
        "Currency":"EUR",
        "StatusTimestamp":"2018-09-10T06:24:44.9940000Z",
        "ConfirmedAt":"2018-09-10T06:24:45.0140000Z",
        "Preauth":false
}

Chargeback

In subscription management, a chargeback refers to a financial transaction initiated by a customer who disputes a charge made to their payment method, typically a credit card. Chargebacks are a mechanism for consumers to request a refund for a purchase they believe is incorrect, unauthorized, or fraudulent.

Billwerk+ Transform needs mechanisms to handle and mitigate chargebacks, such as transparent billing practices, dispute resolution procedures, and fraud prevention measures.

• Chargeback is triggered by the end customer,
• Recurring payments get deactivated in the Contract,
• The unconfirmed ledger entry for the payment is confirmed, and the chargeback is registered.

Black- and White-Label Payment Providers

The payment process differs for the so-called black-and-white label providers.

Payment process with Black-Label provider

For payments with a black-label provider such as PayPal, the customer is redirected in the checkout process to the payment provider's site to make or confirm his payment there.

Payment process with White-Label provider

If a white-label provider is used for payment, it remains largely invisible to the customer. Nevertheless, payment providers are directly involved in the payment process.

If you have configured a white-label provider, e.g., for credit card payment, its JavaScript bridge is automatically available to you in SubscriptionJS and on the hosted signup and customer portal pages.

The payment provider's JavaScript bridge is used for direct communication between the customer's browser and the payment provider's interface. This transfers the payment data from the customer browser directly to the payment provider, checks the data, and returns a success or error message.

Sensitive credit card data such as the credit card number and the CVC are never transferred to Billwerk+ Transform and are therefore not stored in the billwerk system. Billwerk only receives a "pseudo number" shortened to the last four digits and the expiry date of the credit card and the card issuer (e.g., VISA or Mastercard).

After successfully verifying the payment data, Billwerk+ Transform receives a payment token, which is then used to communicate further with the payment provider.