Coris is building the world’s first AI-powered SMB risk management platform. Today, we’re excited to announce our integration with Adyen for Platforms (AfP).
Now, enterprise software companies using AfP for embedded payments can combine their Adyen merchant data with other data sources to automate their risk management. The best part? There is no code involved at any point in the process.
Read on to learn more about the integration, or check it out yourself.
Context
AfP makes it significantly easier for software companies to launch embedded payments products. However, there are two critical issues software companies face as they scale with AfP:
- Although AfP offers some basic risk management support, it doesn’t satisfy all of the requirements software companies have. As a result, many software companies own underwriting, credit risk, and fraud risk management themselves, often for the first time.
- Merchant data inside Adyen is extremely useful for underwriting and risk management, but it’s difficult to extract insights from this data. Teams often resort to manual data extraction and analytics (think spreadsheets), which can be time and resource intensive.
Up until now, there hasn't been a comprehensive, automated system for merchant data analysis and risk management.
How it works
Our Adyen integration allows risk and payments teams to pull merchant data from AfP into Fuzio’s rule engine and automate risk management with custom risk rules and actions.
Here is a high-level overview of how the integration works:
- The risk (or payments) team provides Coris with an API key from Adyen.
- The team chooses events they’d like to monitor in the form of webhook alerts. We currently support over a dozen Adyen webhook events, including key account changes (e.g., payments, balance information, chargebacks, disputes, payouts).
- Teams can use Fuzio’s rule engine to create rules for these webhook events based on certain conditions. Customers can check rules in real-time, and they can check for multiple rules at a time. Rules can be associated with Adyen events (such as elevated chargebacks or refunds), third-party data sources (Google, Yelp), or even internal platform data from Redshift or Snowflake (e.g., past due subscription payments).
- Customers can set up actions to automatically occur if certain rules are met, such as forwarding cases to manual review or actioning the account.
Use cases
Let’s walk through a few common use cases.
SMB onboarding & underwriting
- When a new embedded payments account is created, platforms can set up rules checking against Coris’s SMB data or other data sources to perform their custom underwriting processes. If an SMB does not pass this automated underwriting, platforms can trigger actions such as a manual review.
- This automated process can accelerate onboarding times and reduce the number of manual reviews. Now, platforms can funnel a minority of merchants for manual reviews, instead of reviewing each merchant manually.
Ongoing Monitoring
- When a payout is scheduled or initiated for an SMB, platforms can automatically check multiple data sources before deciding to release the payout. For example, they can check the chargeback history on Adyen, or whether the business is still open on Google or Yelp.
- If the SMB meets at least one of these conditions – say, they’ve exhibited elevated chargeback rates or reported a change in business status on Google / Yelp – platforms can automatically trigger a manual review for the merchant and / or stop the payout outright.
Building redundancies
- If a software platform uses multiple payment processors (e.g., Adyen and Stripe), it can orchestrate payments risk management for both inside of Coris. This allows platforms to avoid a single point of failure (by relying on just one processor), while streamlining the operational processes.
What’s next?
We’re constantly adding new integrations in order to become the world’s leading SMB risk management platform. Check out our existing integrations here.
Reach out if you’d like to learn more about our Adyen integration, or to request a new integration.
Wrapping Up
We hope this guide is helpful for getting started with the OS1 and Google Cartographer. We’re looking forward to seeing everything that you build. If you have more questions please visit forum.ouster.at or check out our online resources.
This was originally posted on Wil Selby’s blog: https://www.wilselby.com/2019/06/ouster-os-1-lidar-and-google-cartographer-integration/