Automations
You can trigger automations in Rebilly based on almost any event, from gateway routing based on transaction volume to sending past-due invoice reminders or accepting transactions based on risk scores. Use automations to help you manage your business more efficiently.
In Rebilly, an action is an operation that executes when an event occurs. Actions and event conditions are defined in rules and binds.
For a list of all events, see Events, Email notification events, and Tagging events.
Example automations
The following tutorials describe common automations in Rebilly:
- Automate emailing invoices: How to set up common email invoice automations.
- Create a velocity limit: How to create a velocity limit. When the limit is reached, a blocklist record is created for the related payment card, blocking it for a period of one hour. Transaction velocity is the number of transactions that occur within 24 hours.
- Set up gateway routing: How to set up gateway routing. Payment gateway routing is the process of dynamically routing transactions between payment gateways, based on real-time data and selected parameters.
- Display payment methods by location: How to configure which payment methods are displayed to the customer at payment, based on their geographic location.
- Set usage limit notifications for metered billing: How to set usage limit notifications for metered billing. When a customer reaches a usage limit, an email notification is sent to the customer.
Gateway automation
Rebilly provides a number of gateway automations to help you manage your payment gateways. Some common gateway automations are described in this section.
Gateway routing
When you have more than one gateway account connected to Rebilly, you can use payment gateway routing to dynamically route transactions between payment gateways, based on real-time data and selected parameters. Payment routing helps minimize processing fees and maximize transaction approval rates, while also improving the reliability of your payment system. For example, if one payment gateway fails or is down, you can configure transactions to automatically route to another preferred payment gateway. For more information, see Payment gateway routing.
Routing examples:
- Payment card type: Some payment gateways provide better rates with certain banks based on pre-pay and debit cards, for example.
- Transaction cost: Payment cards have different fee structures or rates that are negotiated as you move up in volume. You can route these payments to optimize rates and costs.
- Approval rate: Some payment gateways have better approval rates in certain regions or with certain banks. You can route transactions to optimize for approval rates.
Automate at point of sale
Rebilly provides several events that can be used to trigger automations at the point of sale. For example, you can configure a payment gateway automation that displays specific payment methods to customers at the point of sale based on their geographic location. For more information, see Display payment methods by location.
Volume limits
Use volume limits to limit the amount of money, or number of transactions, that a gateway account can process daily or monthly. When a volume limit is reached, the gateway account enters scheduled downtime until the frequency period expires.
If a new transaction is initiated during this period, and a weighted distribution rule is configured, the gateway with ongoing downtime is not considered. If no gateway account is available, the transaction is declined.
Schedule downtime
Use the schedule downtime feature to divert incoming transactions to another available gateway until the downtime expires.
Approval window Time To Live (TTL)
Use Approval window Time To Live (TTL) to specify the amount of time in which an offsite transaction must be approved before it is automatically abandoned.
Dynamic Currency Conversion (DCC)
Use dynamic currency conversion to allow your customer to pay in their local currency and to create a transparent and convenient payment experience. You can also add a markup to the conversion rate to help increase your profit margin.
Reconciliation window
Use the reconciliation window to specify the amount of time in which an approved transaction must be reconciled before it is automatically abandoned.
3 Domain Secure (3DS)
Activate 3DS on payment gateway transactions to provide a security layer for online credit and debit card transactions and help validate cardholders. The cardholder authenticates their card against the website of the issuing bank.
Sticky gateway accounts
Use sticky gateway accounts to specify that all future payments from new payment instruments must be processed by the same payment gateway that processed their first transaction.
Additional filters
Use additional filters to set additional filters for your payment gateways.
Webhooks
Use webhooks to notify your systems when certain events occur and to collect event information. Webhooks are triggered by events that occur in Rebilly, such as a new customer being created, a payment being processed, or a subscription being canceled. Rebilly sends notifications through HTTP and HTTPS methods to a URL of your choice. For more information, see Webhooks.
Email notifications
Email notifications are targeted email messages, that can be plain text or HTML.
Use organization email notifications to get informed when events related to your organization occur. The following events are supported:
- User access changes: Occurs when a user gains access to the organization or the permissions change.
- API access changes: Occurs when an API key provides access to the organization.
Use customer email notifications to keep customers informed on events, and to inform them of events that may require action on their end. Email notifications are configured to send automatically when a system event occurs, or by broadcasting to a select group of customers. For a list of all available email notification events, see Email notification events.
Email notifications can also be used to notify teammates about new customers, blocklist matches, risk score changes, and more. For more information, see Email notifications.
Automated tagging
Use automated tagging to automatically tag customers based on specific events or conditions. For example, you can tag customers who have not paid an invoice within a certain time frame, or customers who have a high risk score. For more information, see Automated tagging.