Skip to content

Payment methods

One screen for every payment method your shop and your invoices can offer — credentials, channels and appearance in one place.

Configuration → General → Payment methods is the single place where you set up how you get paid. It lists every method a customer can choose — in your online shop, or on an invoice payment link — and holds each method's credentials, its channels and its storefront appearance on one page.

url: configuration/paymentmethods crop: h2, table.payment-methods The Payment methods list, showing each method with its status and its Shop and CRM columns.

What changed

Setting up a payment provider used to mean visiting up to three screens, none of them the one you would guess:

  • Shop → Integrations held the PayPal, Payrexx and PostFinance Checkout credentials.
  • Shop → Payment types held the Saferpay and Wallee credentials in a strip at the top, and the label, icon, sort order and visibility of every method in a grid below it.
  • Because both pages sat inside the Shop module, an account on a plan without the shop could not configure a payment provider at all.

The grid was also a free-form list: an Add button let you create a second and a third row for the same method, with no indication which one your checkout would actually use.

Now there is one page, outside the Shop area:

  • The list is fixed. It is the same set of methods for every account, so there is no Add and no Delete — and no way to end up with three PayPal rows. Turning a method off is simply unticking both channels, which is reversible and never affects an order that already used it.
  • Credentials and appearance are on the same form. Everything that makes one method work is on that method's own Configure page.
  • You no longer need the shop to take money. The page opens on any plan; the Shop column and the storefront sections are simply hidden when you don't have the module.

The old addresses still work — Shop → Payment types now redirects here, and Shop → Integrations keeps its feed, WineSearcher and Google Merchant settings and links across to this page.

Reading the list

ColumnWhat it tells you

Method

The payment method's name.

Status

Whether the method is ready to use.

Shop

✓ when the method is offered in your online shop.

CRM

✓ when the method may be offered on an invoice payment link.

The Status column is honest about four cases:

  • No configuration needed — the method has no credentials at all (Invoice, Prepayment, Cash, TwintManual). Tick a channel and it works.
  • Configured — credentials are stored and the method is ready.
  • Not configured — no credentials yet. Enabling a channel will not help until you enter them.
  • Enabled but not configured — shown in red. The method is switched on for a channel but has no credentials, so customers are being offered a method that cannot take their money. This is the screen that tells you; fix it by entering the credentials or by unticking the channel.

A dash in the CRM column means the method can never be offered on a payment link — a link cannot settle itself with "pay by invoice".

Configure one method

Click Configure on the method's row. Which sections you see depends on the method and on whether you have the Shop module.

url: configuration/paymentmethods/edit?type=7 steps: - fill: input[name="SaferPay.CustomerId"]|EXAMPLE-123456 - fill: input[name="SaferPay.Username"]|EXAMPLE-API-USER - fill: input[name="SaferPay.Password"]|EXAMPLE-SECRET - fill: input[name="SaferPay.TerminalId"]|EXAMPLE-17900001 maxheight: 2400 The Configure page for a payment provider, with its Credentials, Channels, Storefront appearance and Documents on checkout sections.

Credentials

The provider's own fields, exactly as your provider issues them:

  • PayPal — API username, API password, API signature, and the environment.
  • Payrexx — instance name and API secret.
  • PostFinanceCheckout — space ID, application user ID and application user key.
  • SaferPay — customer ID, JSON API username, JSON API password, terminal ID and the environment. Create the JSON API user under Settings → JSON API in the Worldline Backoffice; your ordinary Backoffice login will not work here. The section links straight to the test and live Backoffice.
  • Wallee — space ID, application user ID and application user key.

Methods with nothing to configure (Invoice, Prepayment, Cash, TwintManual) have no Credentials section.

Google Pay

Providers that can take Google Pay inside the checkout page show a Google Pay section: a Google merchant ID from the Google Pay & Wallet Console and the merchant name shown in the Google Pay sheet. There is no separate switch — Google Pay appears in your checkout as soon as the provider supports it and these fields are filled in. The merchant ID is only needed for live payments. Providers that offer Google Pay on their own payment page instead say so in this section.

Channels

Two checkboxes decide where the method may be offered:

Storefront appearance

Only with the Shop module. Set the sort order that positions the method in your checkout, and its name per language — pick a language in the Language dropdown and type the name your customers see in that language. Where the method has an icon, it is shown between the sort order and the language picker.

Documents on checkout

Only with the Shop module. Tick which documents Vinosoft creates automatically when an order is paid with this method: order confirmation, delivery note, invoice. A method used for advance payment typically generates only an order confirmation; a method that takes the money immediately can safely generate all three.

Click Save. Vinosoft stores the method and takes you back to the list, where the Status and channel columns already show your change.

Payment links

Below the method list, the Payment links block controls how invoice payment links behave for the whole account. Which methods a link may offer is the CRM column above — this block is only about the links themselves.

url: configuration/paymentmethods crop: h3, h3 + .form-wrapper The Payment links block, with the offer switch, the link lifetime, the notification addresses and the payer-receipt option.
  • Offer payment links on invoices — the overall switch. Leave it on; with nothing ticked in the CRM column there is nothing to offer anyway, so switching it off is mainly a way to withdraw the feature from your team.
  • New links are valid for (days) — how long a newly created link works. Leave it empty (or set it to 0) for links that never expire. Existing links keep the expiry date they were given.
  • Notify these addresses — the addresses notified whenever a customer pays through a link. One per line; a pasted comma- or semicolon-separated list is accepted too. Leave it empty and the notification goes to the invoice's seller, or failing that to the address your Vinosoft mail is sent from.
  • Email the payer a receipt — sends the customer a short confirmation after a successful payment. It is a confirmation, not a receipt for accounting purposes, and it goes to the invoice's own contact address.

Click Save. These settings apply to every invoice in your account.

Was this article helpful?

Configure payment methods in Vinosoft