Use Rebilly to optimize and orchestrate your payments and related processes. When a merchant integrates Rebilly, they simplify and optimize their payments, compliance, data, and processes.
Rebilly provides a single technical structure for processing online payments and enables merchants to centrally manage gateways, services, and vendors within a single system. This enables E-commerce platforms to work with a single API key and also enables increased scalability and compliance with reduced overhead.
Allow your development teams to focus on core business processes and needs. Free them from setting up and managing individual payment gateways, processes, and services. Improve the consumer experience and the ROI on each transaction.
All businesses that accept card payments must comply with the Payment Card Industry Data Security Standards (PCI DSS) standards. Obtaining and maintaining PCI compliance is a complex and expensive process. By using Rebilly you reduce security related expenses by offloading most of your PCI-DSS compliance burden.
Rebilly is a level 1 PCI-DSS service provider, data security is one of our highest priorities. We go beyond industry standards to meet a high level of data security at every layer, from server hardening techniques and network segmentation to extensive data integrity logging, secure coding practices, and rigorous testing.
Rebilly is also SOC 2 compliant. This means that we ensure sensitive data is managed securely within the context of SaaS and other cloud-based services.
Additionally, to make your system more secure, Rebilly provides the ability to tokenize and vault cards and process them, along with secure SDKs in iframes to reveal and capture card data in the merchant website or app. Rebilly enables you to isolate your system from managing or processing card data.
Rather than building infrastructure to accommodate x number of Payment Service Providers (PSP), x number of payment gateways, x number of payment methods for each payment gateway, tokenization, protocols for each integration, and adhering to PCI-DSS — when you integrate Rebilly you get all of this out-of-the-box. Building this kind of infrastructure is complex and expensive to implement, especially as you expand to new markets.
Rebilly supports more than 180+ payment gateways and supports 130 payment methods including ACH, PayPal, and Bitcoin. If you would like to add a payment integration that’s not in our list, we'll add it for free! Just request a new payment gateway integration.
Payment gateway routing is the process of dynamically routing transactions between payment gateways, based on real-time data and selected parameters. Payment routing helps you to minimize processing fees and maximize transaction approval rates.
Transaction 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.
- Route based on approval rates.
Transaction routing also improves 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.
By using Rebilly to manage payment integrations and PCI compliance and security, you can quickly scale and expand into new markets without the overheard of complex and expensive infrastructure and compliance burden.
For example, a US based merchant is expanding into the EU market and must adhere to the PSD2 laws and other requirements for each country. Rather than creating new payment flows, infrastructure, and policies for this market — they can use Rebilly to simplify the process, reduce costs, and save time.
Rebilly helps protect you from fraud by providing the following fraud protection:
- Transaction risk scoring: Spots potential fraud before it happens.
- Device fingerprinting: Helps ensure that devices that are used to complete payments are associated with the customer.
- Managing blocklists: Stops known offenders from generating more transactions.
- Recording disputes: Manages your chargeback ratios and automate canceling subscriptions and dispute handling.
- Automating the dispute process: Saves time and reduce human error.
- Managing evidence: Helps you win disputes.
Rebilly also provides a Know Your Customer (KYC) and Anti-Money laundering (AML) add-on.
Rebilly provides a single technical structure for processing online payments and enables merchants to centrally manage gateways, services, and vendors within a single system. Rebilly also provides customer and payment data management, billing and invoice management, automation, and comprehensive analytics and reporting capabilities on Performance Indicators (KPIs), revenue, logs, and more.
Reconciliation ensures the accuracy and validity of financial information by comparing transactions and activity to supporting documentation. The process may also involve resolving any discrepancies that are discovered.
Rebilly helps to keep your payment data secure and reduces processing costs by providing tokenized payments.
Tokenization is the process of replacing Payment Card Numbers (PANs) with unique and non-sensitive strings of numbers. A payment token is a short-lived unique string of numbers that represents a PAN.
Rebilly also supports storing and re-using third-party tokens. Tokenized payments can produce higher approval rates and ensure less fraud.
Rebilly vaults cardholder data and supports the portability standard. Rebilly is committed to making sure clients have full access to their data when they need it. The safe, secure, free-flow of data makes it a better online experience for everyone.
3DS is an additional security layer for online credit and debit card transactions. 3D stands for the three domains that interact using the protocol: the merchant or acquirer domain, the issuer domain, and the interoperability domain.
3DS stops fraudsters from enrolling cards they do not own by adding another layer of authentication, kind of like Two-Factor Authentication (2FA) for payments. For example, someone steals a payment card, enrolls it, and obtains an associated token. 3DS validates the card number when it's entered into a merchant's website or app, and completes checks to ensure that the payment card owner is who they say they are. If it's not possible to do this discretely, a challenge process is used to direct the cardholder to the related bank or card internet banking account to authenticate. The majority of the time it is completed discretely using device fingerprinting, patterns, IP address, and so on.