# Use Bayarcash in Make

> Add the Bayarcash app to your Make organization with its invitation link, connect your account and use Bayarcash in your scenarios.
>
> Source: https://docs.bayarcash.com/make/

[Make](https://www.make.com) (formerly Integromat) connects apps in visual workflows called scenarios. The Bayarcash app for Make lets a scenario work with your Bayarcash account without code.

## Before you start

You need these before you add the app:

- A Make account. The app installs in one of your Make organizations.
- An approved Bayarcash merchant account, or a sandbox account for tests.
- Your Bayarcash keys from the merchant dashboard. See [Find your API keys](/api-keys/).

## Add the Bayarcash app to Make

Bayarcash shares its Make app with an invitation link, not through the public Make app list. To add it:

1. Sign in to Make.
2. Open the [Bayarcash invitation link](https://www.make.com/en/hq/app-invitation/2b07ed861f787c1e498d49d681944314).
3. Choose the organization where you build your scenarios.
4. Install the app.

The app is then available in that organization only. For another organization, open the link again.

## Connect your Bayarcash account

Make asks for a connection the first time you use a Bayarcash module. To make the connection:

1. In a scenario, add a module and search for **Bayarcash**.
2. Choose the module that you need.
3. Create a new connection and enter the Bayarcash keys that it asks for.
4. Save the connection.

Use sandbox keys while you test. Change to live keys only when a test payment works from start to end.

## Receive payment results in Make

Bayarcash sends the result of each payment to the callback URL of that payment. To act on the result in Make:

1. Start a second scenario with the **Webhooks** app of Make, and copy its address.
2. When you create the payment, put that address in the callback URL field, if the module has one.
3. Verify the `checksum` with your API Secret Key before you trust the data. See [Verify callbacks and checksums](/callbacks-and-checksum/).

## Tips

- **Keep the order number unique for each payment.** It links each callback to the row that started the scenario.
- **Use one connection for each environment.** Give each connection a clear name, so a test never uses live keys.

## Common issues

### I cannot find Bayarcash when I add a module to a scenario. Why?

The Bayarcash app is not in the public Make app list. It is shared with an invitation link. Open the invitation link (https://www.make.com/en/hq/app-invitation/2b07ed861f787c1e498d49d681944314) again and install the app in the organization where you build the scenario.

### The invitation link only shows a Make sign-in page. What do I do?

Sign in to Make, or create a Make account. Then open the invitation link again. The app installs in a Make organization, so you must sign in first.

### Which Bayarcash keys does the connection need?

Use the keys from the same merchant dashboard as the payments: the sandbox keys for tests and the live keys for real payments. See Find your API keys (/api-keys/).