# Payment methods

Payment methods are the types of payment that customers use to pay for goods or services. These methods include credit and debit cards, digital wallets like Google Pay™ and Apple Pay, bank transfers, direct debits, ACH, Wire, buy-now-pay-later services, and more.

Payment methods are processed by payment gateways, which are services that authorize and process payments. In Rebilly, you configure payment methods on payment gateways. For more information, see [Set up a payment gateway](/docs/settings/set-up-a-gateway).

## Supported payment methods and gateways

Rebilly supports more than 167 payment methods. For a full list of supported payment methods, see [Payment methods](/payment-methods). If you would like to use a payment method that is not in the list of supported payment methods, Rebilly will integrate it for you at no additional cost. For more information, see [Send an integration request](/docs/settings/integration-requests#send-an-integration-request).

## Configure payment methods

In Rebilly, you configure payment methods and digital wallets on payment gateways. To set up a new payment gateway, or to configure payment methods for an existing payment gateway, see [Set up a payment gateway](/docs/settings/set-up-a-gateway).

## Payment method automations

Two events trigger payment method automations in payment forms:

- [Ready to pay requested](/docs/automations/event-types#ready-to-pay-requested): Executes when a customer requests to pay or to deposit funds.
- [Ready to payout requested](/docs/automations/event-types#ready-to-payout-requested): Executes when a customer requests a payout.


For both events, you can configure conditions on when the event must execute, and the actions to take when the event is executed. For example, you can automate which payment methods are displayed to the customer based on their geographic location, or set the order in which payment methods are displayed. For more information, see [Payment method display order](#payment-method-display-order) and [Display payment methods by location](#display-payment-methods-by-location).

### Payment method display order

This process describes how to configure which payment methods are displayed in a payment form and the order in which they are displayed.

1. Optionally, if you do not have more than one payment gateway configuredIf you are testing in the sandbox environment, a test payment gateway called `TestProcessor` is already configured to use the payment card payment method.
Set up another TestProcessor payment gateway, and configure it to use a different payment method. For more information, see [Set up a payment gateway](/docs/settings/set-up-a-gateway).
2. Create an automation on the 'ready to pay requested' event:  1. In the left navigation bar, press .
  2. In the **Rules engine** section, press **Rules engine**.
  3. Press **Core events**.
  4. Press the **Ready to pay requested** event.
  5. Press **Rule set**, then press **Create rule**.
  6. In the **Name** field, enter a unique name to help differentiate between multiple rules.
  7. Optionally, to add labels that help you identify the rule: In the **Labels** field, add one or more labels.
  8. Optionally, to not stop further processing after this rule is executed: clear the **Stop further processing** checkbox.
3. Configure an action to adjust the order of displayed payment methods  1. In the **Actions** section, press **Add action**, then select the **Adjust ready to pay** action.
  2. Specify which payment methods to display when a customer requests to pay.
  3. To adjust the order in which payment methods are displayed, drag and drop the payment methods in the list.
  4. Optionally, to display payment methods that are associated with the customer's active payment instruments at the top of the list: Select the **Prioritize active payment instruments** checkbox.
  5. Press **Save rule**.


### Display payment methods by location

This process describes how to configure which payment methods are displayed to the customer in a payment form based on their geographic location. You can also prioritize the customer's active payment methods.

To complete this process, an active gateway is required. If you are testing in the sandbox environment, a test payment gateway called `TestProcessor` is already configured. For more information, see [Set up a payment gateway](/docs/settings/set-up-a-gateway).

1. Create an automation on the 'ready to pay requested' event:  1. In the left navigation bar, press .
  2. In the **Rules engine** section, press **Rules engine**.
  3. Press **Core events**.
  4. Press the **Ready to pay requested** event.
  5. Press **Rule set**, then press **Create rule**.
  6. In the **Name** field, enter a unique name to help differentiate between multiple rules.
  7. Optionally, to add labels that help you identify the rule: In the **Labels** field, add one or more labels.
  8. Optionally, to not stop further processing after this rule is executed: clear the **Stop further processing** checkbox.
2. Set conditions based on the customer's geographic location.  1. In the **Conditions** section, clear the **No conditions** checkbox.
  2. Select this filter: `RiskMetadata > Country`.
  3. Select this condition: `is in`.
  4. Select a country.
  5. Optionally, to add more filters, press **Add filter**.
3. configure which payment methods are displayed to the customer  1. In the **Actions** section, press **Add action**, then select the **Adjust ready to pay** action.
  2. Specify which payment methods to display when a customer requests to pay.
  3. Optionally, to display payment methods that are associated with the customer's active payment instruments at the top of the list: Select the **Prioritize active payment instruments** checkbox.
  4. Press **Save rule**.


To automatically assign a payment gateway based on customer location, and other data, see [Set up payment gateway routing](/docs/settings/gateway-routing).