FAQs

Q: Some fees, such as the client setup fee, are not attached to an account type. How does the billing engine identify the currency of the fee?

A: The currency will be the client's default currency, configured in the company settings.

Q: Some fees are not attached to an account type (e.g., client setup fee, new user fee, etc.). How does the billing engine decide which account will be charged?

A: These fees are charged from the main account associated with the fee's currency.

Q: What is the difference between an interledger fee and an internal transfer fee?

A: An interledger fee applies to a payment scheme provided by the banking provider; for example, with Railsr, payments between accounts of the same partner product (not necessarily under the same owner) utilize the interledger scheme.

In contrast, an internal transfer refers specifically to payments between accounts belonging to the same owner. The applicable payment scheme varies depending on the currencies of the source and destination accounts.

Automatic Retry Logic

Automatic retry refers to the system’s capability to repeatedly attempt billing charges after an initial failure until the transaction succeeds.

Related FAQs:

Q: Has automatic retry been implemented for both recurring and fixed transactions?

A: Yes, automatic retry applies to both recurring and fixed transactions.

_Q: If card issuance billing fails, will the system retry charging the card account or the account set up by user to charge the account issue fee?

A: The system will retry charging the account initially set up to pay the fee.

Q: How many retry attempts are currently configured?

A: There is no limit on retry attempts; the system continues retrying until the transaction is successful.

Billing Retry Logic Explanation

Currently, the billing retry process functions as follows:

• When a billing charge fails, the status of the billing entry (billed=false) remains unchanged. At this stage, no billing transaction (billing tx) is generated.
• The same billing entry is automatically retried the next day. If successful, a billing transaction is created with a "withheld" status.
• The banking provider sends a webhook notification to update the billing transaction status, making the transaction visible to users only after successful processing.

This logic applies consistently to both:

• Merchants being charged.
• Billing fee account holders.

Users only see billing transactions upon successful completion. Until successful, no billing transaction is visible.