---
title: "Payments"
description: "Connect an online payment provider so customers can pay for a rental by card: Stripe, Plata by mono, LiqPay, or WayForPay."
canonical_url: "https://requiply.com/docs/en/guides/settings/integrations/payments"
---
# Payments

> Connect an online payment provider so customers can pay for a rental by card: Stripe, Plata by mono, LiqPay, or WayForPay.

The **Payments** page is where you connect Requiply with online payment providers. Connected providers let customers pay online during booking, checkout, invoice, and payment-link flows.

You can find this page under **Settings → Integrations → Payments**.

![Payments integrations page](https://requiply.com/docs/assets/settings/integrations/payments/image.png)

## Why payments matter

Payment integrations control which online payment providers are available for your organization. Without an active provider integration, Requiply can still support non-online payment workflows, but customers cannot use that provider for hosted online checkout.

Connected payment providers can be used across:

- **Client portal checkout** - online payment methods can be enabled only after the matching provider is configured.
- **Bookings** - online payment attempts create payment records connected to the booking.
- **Invoices and payment links** - customers can open provider payment URLs from payment records.
- **Payment status updates** - provider callbacks update the booking payment status after a payment succeeds, fails, expires, or is cancelled.

## What you'll see

The page groups the providers into two sections:

- **Global providers** - Stripe, for card payments in any of the 14 Requiply currencies.
- **Ukrainian providers** - Plata by mono, LiqPay, and WayForPay.

Each provider card includes:

- **Provider name** and logo.
- **Setup status** - either **Configured** or **Not configured yet**.
- **Tutorial** - opens Requiply's step-by-step setup guide for that provider in a new browser tab, in your interface language. The Stripe card has no tutorial link; its setup steps are in [Stripe](#stripe) below.
- **Setup** - opens the credential form for that provider. Once the provider is configured, the button reads **Manage** and opens the same form.

The current provider catalog includes:

<table>
<thead>
  <tr>
    <th>
      Provider
    </th>
    
    <th>
      Credentials required
    </th>
    
    <th>
      Supported currencies
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Stripe
      </strong>
    </td>
    
    <td>
      Secret API key and webhook signing secret
    </td>
    
    <td>
      All 14: CHF, DKK, EUR, GBP, INR, ISK, JPY, MKD, NOK, PLN, RON, TRY, UAH, USD
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Plata by mono
      </strong>
    </td>
    
    <td>
      Monobank token
    </td>
    
    <td>
      No Requiply catalog restriction
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        LiqPay
      </strong>
    </td>
    
    <td>
      Public key and private key
    </td>
    
    <td>
      UAH, USD, EUR
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        WayForPay
      </strong>
    </td>
    
    <td>
      Merchant Login, website domain, and Merchant Secret Key
    </td>
    
    <td>
      UAH
    </td>
  </tr>
</tbody>
</table>

<note>

The provider card shows **Configured** when the organization has an active integration for that provider. If no providers are connected yet, all cards remain visible and show **Not configured yet**.

</note>

## Opening a tutorial

Click **Tutorial** on a provider card when you need help finding credentials in the provider account. Requiply opens its own step-by-step guide for that provider in a new tab — the English or Ukrainian version, matching your interface language.

Setup guides:

<table>
<thead>
  <tr>
    <th>
      Provider
    </th>
    
    <th>
      Guide
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Plata by mono
      </strong>
    </td>
    
    <td>
      <a href="https://requiply.com/uk/blog/monobank-integration" rel="nofollow">
        Monobank integration guide
      </a>
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        LiqPay
      </strong>
    </td>
    
    <td>
      <a href="https://requiply.com/uk/blog/liqpay-integration" rel="nofollow">
        LiqPay integration guide
      </a>
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        WayForPay
      </strong>
    </td>
    
    <td>
      <a href="https://requiply.com/uk/blog/wayforpay-integration" rel="nofollow">
        WayForPay integration guide
      </a>
    </td>
  </tr>
</tbody>
</table>

## Setting up a provider

Click **Setup** on a provider card to open the setup dialog. The dialog shows the selected provider logo and the credentials Requiply needs for that provider.

After you click **Save**, Requiply checks the credentials with the payment provider before storing the integration. If verification succeeds, the provider becomes active for your organization and the card can move to **Configured**. If verification fails, Requiply shows an error and does not save the provider as active.

Click **Cancel** to close the setup dialog without saving changes.

<warning>

Copy credentials from the correct live merchant account. Invalid tokens, missing permissions, or keys from the wrong provider account can prevent setup from saving.

</warning>

## Provider fields

### Plata by mono

<table>
<thead>
  <tr>
    <th>
      Field
    </th>
    
    <th>
      What it means
    </th>
    
    <th>
      Input type
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Monobank token
      </strong>
    </td>
    
    <td>
      Token used to connect Requiply with the organization's Monobank payment capability.
    </td>
    
    <td>
      Password
    </td>
  </tr>
</tbody>
</table>

Requiply verifies the token with Monobank before saving it. A token with invalid permissions or an invalid value is rejected. Tokens from the Monobank business cabinet, including legal-entity accounts, verify as well. If such a token was refused before, try saving it again.

### LiqPay

<table>
<thead>
  <tr>
    <th>
      Field
    </th>
    
    <th>
      What it means
    </th>
    
    <th>
      Input type
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Public key
      </strong>
    </td>
    
    <td>
      Public LiqPay key used in payment requests.
    </td>
    
    <td>
      Text
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Private key
      </strong>
    </td>
    
    <td>
      Private LiqPay key used to sign API requests and webhook checks.
    </td>
    
    <td>
      Password
    </td>
  </tr>
</tbody>
</table>

Requiply verifies the LiqPay public and private keys before saving the provider.

### WayForPay

<table>
<thead>
  <tr>
    <th>
      Field
    </th>
    
    <th>
      What it means
    </th>
    
    <th>
      Input type
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Merchant Login
      </strong>
    </td>
    
    <td>
      The merchant account login from WayForPay.
    </td>
    
    <td>
      Text
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Website domain
      </strong>
    </td>
    
    <td>
      The merchant website domain, such as <code>
        requiply.com
      </code>
      
      .
    </td>
    
    <td>
      Text
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Merchant Secret Key
      </strong>
    </td>
    
    <td>
      Secret key used to sign WayForPay requests and webhook responses.
    </td>
    
    <td>
      Password
    </td>
  </tr>
</tbody>
</table>

Requiply verifies the WayForPay merchant details before saving the provider.

### Stripe

<table>
<thead>
  <tr>
    <th>
      Field
    </th>
    
    <th>
      What it means
    </th>
    
    <th>
      Input type
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Secret API key
      </strong>
    </td>
    
    <td>
      The secret key from your Stripe account, starting with <code>
        sk_live_
      </code>
      
       (or <code>
        sk_test_
      </code>
      
       for testing). Not the publishable key that starts with <code>
        pk_
      </code>
      
      .
    </td>
    
    <td>
      Password
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Webhook signing secret
      </strong>
    </td>
    
    <td>
      The signing secret of the webhook endpoint you add for Requiply in Stripe, starting with <code>
        whsec_
      </code>
      
      . Requiply uses it to check that payment updates really come from Stripe.
    </td>
    
    <td>
      Password
    </td>
  </tr>
</tbody>
</table>

Requiply verifies the secret key with Stripe before saving it. The webhook signing secret is not checked at save time: if it is wrong or the endpoint is missing, customers can still pay, but the payment stays **Pending** in Requiply because the updates from Stripe never arrive or are rejected.

#### Add the Requiply webhook in Stripe

Stripe tells Requiply about paid, failed, expired, and refunded payments through a webhook. Add it before you save the integration:

1. In the Stripe Dashboard, open **Developers → Webhooks** and add an endpoint (newer Dashboards call it an event destination).
2. Set the endpoint URL to `https://app.requiply.com/api/payment-integrations/stripe/update-status`.
3. Select these events: `checkout.session.completed`, `checkout.session.async_payment_succeeded`, `checkout.session.async_payment_failed`, `checkout.session.expired`, and `charge.refunded`.
4. Save the endpoint, reveal its **Signing secret**, and paste it into **Webhook signing secret** in Requiply.

<note>

Test mode and live mode have separate webhook endpoints in Stripe. When you switch from an `sk_test_` key to an `sk_live_` key, add the endpoint again in live mode and save its signing secret together with the live key.

</note>

#### Currencies and amounts

Stripe charges customers in your organization's currency, and all 14 Requiply currencies are supported, including the Indian rupee (INR). JPY is charged in whole yen and ISK in whole krónur, so amounts in those currencies are rounded to a whole unit.

Stripe also has a minimum charge per currency, for example 0.50 USD or EUR, 0.30 GBP, 2.50 DKK, 3.00 NOK, or 50 JPY. A payment link below the minimum is refused. See [Stripe's supported currencies](https://docs.stripe.com/currencies) for the full rules.

## Updating credentials

To replace a token, private key, or merchant secret, click **Manage** on the same provider card, enter the new credentials, and click **Save**. Requiply updates the existing active integration after the new credentials pass verification.

Saved secret values are not displayed on the page after setup. Keep a secure copy in your payment provider account or password manager.

<note>

Secret credentials are encrypted before they are stored.

</note>

## Disconnecting a provider

The current Payments page does not include a visible disconnect or delete action. To change an active provider, click **Manage** and save new credentials for the same provider.

## Where payment integrations are used

<table>
<thead>
  <tr>
    <th>
      Feature
    </th>
    
    <th>
      How the integration is used
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <a href="https://requiply.com/docs/en/guides/online-booking/portal-settings">
        <strong>
          Portal settings
        </strong>
      </a>
    </td>
    
    <td>
      Online payment methods are available only when the matching provider is configured.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Customer checkout
      </strong>
    </td>
    
    <td>
      Enabled online payment providers can appear as customer payment choices.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Bookings
      </strong>
    </td>
    
    <td>
      Online payment attempts create booking payment records with provider, amount, currency, status, and payment URL details.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Payment status
      </strong>
    </td>
    
    <td>
      Provider callbacks update the payment status after customer or provider events.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Invoices and payment links
      </strong>
    </td>
    
    <td>
      Provider payment links can be attached to payment records for customers to open.
    </td>
  </tr>
</tbody>
</table>

## Common scenarios

### Connect online payments for the first time

1. Go to **Settings → Integrations → Payments**.
2. Choose the provider your organization uses.
3. Click **Tutorial** if you need help finding the required credentials.
4. Click **Setup**.
5. Enter the provider credentials.
6. Click **Save**.
7. Confirm the provider card changes to **Configured**.
8. Go to the [Payments tab of Portal settings](https://requiply.com/docs/en/guides/online-booking/portal-settings#payments-tab) and enable the matching online payment method if needed.

### Update provider credentials

1. Go to **Settings → Integrations → Payments**.
2. Click **Manage** on the provider you want to update.
3. Enter the new token, keys, or merchant details.
4. Click **Save**.
5. Confirm that setup succeeds.

### Troubleshoot a failed setup

If setup fails:

- Confirm the credential values were copied from the correct provider account.
- Check that the provider account is active and allowed to create payments.
- Make sure the organization's currency is supported by the provider you want to use.
- For Stripe, paste the secret key (`sk_...`), not the publishable key (`pk_...`).
- For LiqPay and WayForPay, verify that both public and secret credentials belong to the same merchant account.
- Try opening the provider tutorial and repeating the setup steps from the provider dashboard.

### Stripe payments stay Pending

If customers pay through Stripe but the payment in Requiply stays **Pending**:

- Check that the webhook endpoint in Stripe points to `https://app.requiply.com/api/payment-integrations/stripe/update-status` and listens to the events listed in [Add the Requiply webhook in Stripe](#add-the-requiply-webhook-in-stripe).
- Check that the signing secret saved in Requiply belongs to that endpoint and to the same mode (test or live) as the secret key.
- After fixing the endpoint, click **Manage** on the Stripe card and save the corrected signing secret.

<note>

Configuring a provider does not automatically make it visible to customers everywhere. Customer-facing payment methods are still switched on separately in [Portal settings](https://requiply.com/docs/en/guides/online-booking/portal-settings#payments-tab).

</note>


## Sitemap

See the full [sitemap](https://requiply.com/docs/sitemap.md) for all pages.