Before configuring any payment method, make sure your store is already connected to your Asaas account as described in Initial settings.

Each payment method has specific settings, but some options are shared among all of them, such as API authentication, Webhook, notifications, and logs.

📘
Before starting
We recommend performing the entire configuration initially in the Sandbox environment. After validating the checkout and payment operation, change the configuration to the Production environment.

Common settings

The settings below are present in all or most of the payment methods made available by the Asaas Plugin.

Use this sequence to validate any payment method before making it available to customers:

Access the payment method settings in WooCommerce.
Enable the payment method you want to test.
Confirm that the selected environment is Sandbox.
Check whether the API Key has already been entered in the API settings.
Save the changes.
Make a test purchase using this payment method.
Confirm whether the order received the status configured for open payments.
Wait for payment confirmation by Asaas or simulate the applicable flow in the test environment.
Check whether the order was updated after the Webhook return.
Consult the Debug log if the order is not updated as expected.

View shared settings

Enable / Disable

Defines whether the payment method will be available at the store checkout.

Title

Name displayed to the customer during checkout.

Description

Text displayed below the payment method title.

Order status for open payments

Defines which status will be assigned to the order when the payment has not yet been confirmed.

The available options are:

Awaiting: reduces stock and sends emails to the customer and the merchant.
Pending payment: keeps the order pending without reducing stock or sending notifications.

API

Allows you to select the environment (Sandbox or Production) and enter the API Key.

If this configuration has already been performed according to the Initial settings page, it will not be necessary to repeat it.

Webhook

The Asaas Plugin automatically configures the Webhook after API Key validation.

It is also necessary to enter a contact email to receive notifications if the Webhook queue is interrupted.

Notifications between Asaas and the customer

Allows Asaas to send email and SMS notifications to the customer throughout the charge cycle.

Debug log

Keeps records of the operations performed by the plugin, making it easier to identify errors and provide technical support.

We recommend keeping this option enabled.

Configuring Bank Slip

The bank slip payment method allows you to configure installments, charge validity, and rules for splitting receipts.

💡
When to use
Use bank slip when you want to offer upfront or installment payments in up to 60 installments.

View Bank Slip settings

Installments

Allows you to configure between 0 and 60 installments.

Interest per installment

Defines the interest applied for each number of installments.

Minimum amount per installment

Defines the lowest amount allowed for each installment.

Validity days

Number of days until the bank slip due date after the purchase.

Validity period

Number of days the bank slip will remain available after the due date.

If the field remains empty, the bank slip will not be removed automatically.

Payment split

Allows you to automatically split the amount received between different Asaas wallets.

This functionality is available from version 2.2.0 of the Asaas Plugin.

Configuring Pix

The Pix method has settings related to the charge expiration time and the customer’s payment experience.

⚡
When to use
Pix is indicated for immediate payments, offering automatic confirmation after settlement.

View Pix settings

Expiration period

Defines for how many days the QR Code will be available for payment.

After this period, the charge will be removed.

Pix Copy and Paste

When enabled, in addition to the QR Code, the Pix Copy and Paste code will also be displayed to make payment easier.

Payment split

Allows you to automatically split the amounts received between different Asaas wallets.

This functionality is available from version 2.2.0 of the Asaas Plugin.

Configuring Credit Card

Credit Card offers resources for installments, receivables anticipation, and tokenization.

💳
When to use
Use Credit Card when you want to offer upfront payment, installment payment, or resources such as One-click purchase.

View Credit Card settings

Minimum order amount

Defines the minimum amount for this payment method to be displayed.

By entering 0, Credit Card will be available for all orders.

Installments

Allows you to configure between 0 and 12 installments.

Interest per installment

Defines the interest applied for each number of installments.

Minimum amount per installment

Defines the lowest amount allowed for each installment.

Receivables anticipation

Automatically requests anticipation of charges paid by Credit Card, respecting the rules of the Asaas account.

Payment split

Allows you to automatically split the amounts received between different Asaas wallets.

One-click purchase

Allows the customer’s card to be stored for future purchases.

This functionality depends on the release of card tokenization by the Asaas commercial team.

Checkout validation flow

After configuring a payment method, run a complete checkout test to validate the customer experience and order update in WooCommerce.

Expected result by payment method

Payment method	During checkout	After charge generation	After payment confirmation
Bank Slip	The customer selects bank slip and completes the order.	The order remains with the status configured for open payments.	The Webhook updates the order when the payment is confirmed.
Pix	The customer views the QR Code and, if enabled, Pix Copy and Paste.	The charge remains available until the end of the configured expiration period.	The Webhook updates the order after Pix settlement.
Credit Card	The customer enters the card details and completes the order.	The order follows the result returned by payment processing.	The order is updated according to the confirmation received by the plugin.

Scenarios you should test

Generate an order in Sandbox for each enabled payment method.
Confirm whether the title and description displayed at checkout correspond to the payment method settings.
Validate whether the initial order status corresponds to the option chosen in Order status for open payments.
For bank slip, test the due date configured in Validity days and check whether the validity period meets your operation.
For Pix, check whether the QR Code expires according to the configured Expiration period.
For Credit Card, test the minimum order amount and the configured installment options.
If using Payment split, validate whether the split of amounts occurs before releasing the payment method in Production.
Consult the Debug log when the order does not move to the expected status.

✅
Criteria for migrating to Production
Migrate to Production only after each enabled payment method generates the charge correctly, displays the expected information at checkout, and updates the order after payment confirmation.

📘
Best practices

Configure the plugin initially using the Sandbox environment.

Validate all payment methods before migrating to Production.

Keep the Debug log enabled during deployment.

Use only the payment methods necessary for your operation.

If you use Payment split, validate the distribution of amounts before making the store available to customers.

After any important change in the configuration, make a test purchase to confirm checkout operation.

📚
Continue the configuration
After configuring the payment methods, also see:

Initial settings — store connection with Asaas.

Charge methods — differences between one-time, installment, and recurring charges.

Webhooks — automatic synchronization between WooCommerce and Asaas.

Common errors — resolution of the main integration problems.