LogPay

LogPay is a payment service provider (PSP) for online payment services. This is the software which is used to handle digital payment between the passengers and the provider.

In Control Center, use LogPay credentials in the provider area to store and review the provider-specific LogPay connection details.

For the passenger, LogPay offers payment by credit card, SEPA, and also PayPal (via Braintree).

As a factoring payment service provider, LogPay assumes the default risk for the charges it accepts: once it confirms a charge, later chargebacks and disputes on that charge are LogPay’s concern, not the provider’s or ioki’s. A charge that LogPay reports as unsuccessful, however, is a failed payment that still has to be recovered—either retried and settled by the passenger, or resolved by an operator, who can mark it as payment manually retrieved or payment forfeited on the failed payments page. When initiating a payment, LogPay gives immediate feedback on whether it succeeded; other than that, it has no technical communication back to ioki Platform.

Another advantage of LogPay is that refunds can be triggered within ioki Platform.

In order to set up LogPay as PSP, the provider has to conclude a contract with LogPay beforehand. Since this takes some time, this should be planned at least four weeks ahead. LogPay then provides the necessary information, that is,

  • Client ID (for ioki),
  • Merchant ID (for the provider),
  • Public Key and
  • Secret Key,

and, if PayPal is used, a

  • Braintree Access Token.

With this information, LogPay can easily be set up in Control Center. In the provider settings, in the payment section, choose LogPay as the payment service provider and save. Afterwards, open LogPay credentials in the provider area for the provider.

If no credentials have been set up yet, they can be created by selecting Create new in the dropdown menu.

Here, all IDs and keys listed above must be stored. If payment with PayPal is intended, the Braintree Access Token must also be stored. Once this has been done, LogPay is ready to be used.

Some additional remarks:

  • ioki Platform currently does not support Strong Customer Authentication (SCA). A passenger can not save a credit card as a payment method if SCA is activated.

  • For payments with PayPal, secure elements are not mandatory. Even though ioki Platform supports them and they are generated via the PayPal SDK in ioki Passenger App, this is not a mandatory field. This is because Operator booking would not work in that case.

Permissions: manage_logpay_credentials