Enhanced dynamic billing per payment

Rainforest has enhanced how to configure dynamic payment billing fees per payin to enable your platform to define a separate billing fee for each payment method.

Previously, only a single billing fee could be defined on the payin config. This resulted in the same billing fee to be applied, regardless of the payment method the end user pays with.

When calculating the billing fee utilizing the merchant's billing profiles, Rainforest determines the correct rate and fee to apply based on the payment method the end user pays with. This improvement allows the billing fee defined per payin to be based on the payment method, which now aligns with how merchant billing profiles determine the billing fee.

Merchant billing in the payin config

A rate, rate cap, and fee can now be defined for the following payment methods:

• Card - debit or credit card, including Apple Pay
• ACH - US bank accounts
• Validated ACH - US bank accounts collected by the user authenticating into their online bank account
• Accelerated ACH - US bank accounts accelerated to T+1 deposit timing
• PayPal Wallet - debit or credit cards, and US bank accounts through the PayPal wallet
• Venmo - debit or credit cards, and US bank accounts through Venmo
• PayPal Pay Later - debit or credit cards, and US bank accounts through PayPal Pay Later

When creating the payin config, the merchant_billing object was expanded to support defining a rate, rate cap, and fee per payment method:

"merchant_billing": {
  "rate": 3000,
  "rate_cap": 10000,
  "fee": 30,
  "currency_code": "USD",
  "card": { "rate": 2900, "rate_cap": 10000, "fee": 30, "currency_code": "USD" },
  "ach":  { "rate": 800, "rate_cap": 500, "fee": 0, "currency_code": "USD" },
  "validated_ach": { ... },
  "accelerated_ach": { ... },
  "paypal_wallet": { ... },
  "venmo": { ... },
  "paypal_pay_later": { ... }
}

Each payment method object is optional, allowing you to control the specific payment methods you want to set different rates and fees for.

Card, PayPal, Venmo, and PayPal Pay Later precedence order

When processing a Card, PayPal Wallet, Venmo, or PayPal Pay Later payin, determining the rate and fee will respect the following order of precedence:

1. The respective payment method object in the payin config's merchant billing object
2. The top-level rate, rate cap, and fee in the payin config's merchant billing object
3. The respective payment method rate and fee in the merchant's billing profile

ACH precedence order

Validated ACH

Validated ACH is not currently supported in the merchant's billing profile. By default, the merchant's billing profile ACH rate and fee are used to calculate the billing fees that are applied.

With this feature, a specific Validated ACH rate and fee can be configured on the payin config. Determining the rate and fee will respect the following order of precedence:

1. The Validated ACH payment method object in the payin config's merchant billing object
2. The ACH payment method object in the payin config's merchant billing object
3. The top-level rate and fee in the payin config's merchant billing object
4. The ACH rate and fee in the merchant's billing profile

Accelerated ACH

When an ACH payment qualifies for acceleration, determining the rate and fee will respect the following order of precedence:

1. The Accelerated ACH payment method object in the payin config's merchant billing object
2. The top-level rate and fee in the payin config's merchant billing object
3. The Accelerated ACH rate and fee in the merchant's billing profile

Applied billing

Payins now return the applied rate, rate cap, and fee, along with the source that determined the billing fee. The source will be one of the following:

• MERCHANT_BILLING_METHOD - the payment method object in the payin config's merchant billing object
• MERCHANT_BILLING - the top-level rate, rate cap, and fee in the payin config's merchant billing object
• BILLING_PROFILE - the merchant's billing profile

Please contact support if you have any questions.