Name: Recurly Payments Hub: Your new payment analytics dashboard
Uploaded: 2026-05-07T19:30:27.944Z
Duration: 1 h 52 s
Description: Recurly Payments Hub: Your new payment analytics dashboard

Transcript for "Recurly Payments Hub: Your new payment analytics dashboard": So this different. is different. Oh, we're live. Hi, everybody. Welcome. Welcome. Let us know where you're logging in from today. We have a whole we have so many new faces on today, and we're so glad to see you. And we are incredibly excited about this particular session because we are taking a look at Recurly Payments Hub. It's a brand new payment analytics dashboard that lives in analytics. If you've seen it yet, let us know. There's actually a poll open right now in your chat box to the right asking if you've taken a look at it yet. So we're really curious to see if you've played around in there. We're going to get started pretty quickly here because we have a lot to go through, and we have a lot of space open for q and a today. So once again, welcome. We're excited to have you here, and we are excited to have Jeff and Patrick here to walk you through it. Hey, guys. Since we do have so many new faces, I just wanted to quickly run through the navigate program, just a quick overview. Some of you may not be familiar with it. So if you're brand new, you've never heard of Navigate yet and you just received this email because you are a a Recurly customer, just to let you know, this is actually your Recurly customer success program, and it's built for you, our community of merchants. You can think of this as customer success at scale, and it's basically designed to make sure you have access to education, best practices, feat new features, all the the strategic guidance that our merchants who work one on one with customer success managers get, and ensuring that you get real value out of the platform for your entire journey with us. Hopefully, your entire journey as a subscription business. So what this looks like is you have access to guided learning paths. These are structured on demand content built around built around topics that matter to you in the moment, And I'll explain that in just a second. We also have regular weekly global office hours. These are small sessions that you can just jump into once a week at different times during the week. The, link to the global office hours is in your docs area. Jump in. We'll answer any question you have, help you with strategy, setup, anything you need. Then we also have webinars like this one where we're walking through a new feature. Sometimes we'll hear from other merchants. Sometimes it's just complete strategic guidance from our CSMs. You'll also get monthly communications from us like your merchant scorecards. That is a view of your last fiscal month's performance metrics. You'll receive a calendar from us each month. And behind the scenes, we're actually generating proactive recommendations based on your performance data so that we can reach out to you and let you know what we see you might need. Right now, email is our main method of communication, but you'll also see us in in app pop ups and notifications when we have something special for you. So make sure you add [email protected] to your inbox. We're separate from marketing outreach, so it's good to, keep that white listed. And then anytime you see the name Navigate or our little recurly navigate logo, you'll know that that event, that content, that outreach is coming from us. We are also also iterating and growing our prog program. This is new. So we're open to your feedbacks feedback, recommendations, and we will pivot when we see that you need something different. Okay. So that's our goal. Everything you need to launch, acquire, grow, scale your business, and we want you to have it when you need it, when you want it, and when it means the most for you in your life cycle as a business. I will get off of my soap soapbox now, and we are gonna move into the agenda. Dive right in. So we already did our introduction to Navigate. We're going to introduce Jeff and Patrick today. We actually have a special treat. Patrick is going to host today. Then we're going to take a look at what payments hub actually is, a walk through through the platform, stopping for q and a in between each dashboard. Then we'll end with final q and a and resources and what you need to know. Okay, guys. Alright, everybody. Let's go ahead and dive into the session. Today, we're live, but the demos are recorded. And this is so we can ensure you're getting, a really good set of data. But we are here, and we are going to stop in between for q and a. Drop your q and a in the q and a section. We'll also send you this recording at the end, or afterwards. You'll probably receive it tomorrow, but it may be Monday. And we'll update that learning path that we sent to you with these videos. Okay. Jeff and Patrick, I tried to pull you up early and hand this off. So what I'm going to do is I'm gonna step off stage and allow you two to introduce yourself and take the show from here. Hey, everyone. I'm Jeff Piddlekow, a principal product manager at Recurly. Been at Recurly for about nine months now, and I manage the the evolution and growth and maintenance of all of our connected payment gateways and payment methods. And as you'll see today, our analytics that are behind all of this. And I am Patrick Rizzo, senior customer success manager over here at Recurley. I like to describe customer success as think of it like a payments consultant or a strategy consultant for your subscriptions and payment business. And that's really where we shine is giving that advice to our merchants. So today, what we're going to be discussing is our new payments hub, and I'm excited because I am kind of the data analytics nerd of the customer success department. So when it comes to dashboards, when it comes to data, this is where I really start to love my day to day. What is payments hub? It's probably going to be crossing people's minds. Payments hub builds on all of our existing dashboards. It's a new set of five new dashboards that build on all the data analytics, all the performance analytics that Recurly has always given all of our merchants. And now what we do is expand that into payments, whether that's geographic, whether that's by gateway. We have all sorts of fun filters that we're gonna show you today, but it's really another layer to what we've always been doing to offer you better insights to help inform your business and ensure that you're making data driven decisions as we advise you. So without further ado, I think we are ready for our first introduction. Thanks, Patrick. Today, we'll walk through, each of the, payments of dashboards starting with, the overview. And the format for today is I'll do a quick little introduction, and then we will start a video that walks through each of the dashboards and cards, and we'll take a couple of questions along the way. And, and then we'll save plenty of time at the end for more questions as well. So, Ashley, do you wanna go ahead and start the first demo? Hi. I'm Jeff Piddlekow, principal product lead for payments at Recurly. And today, I'm gonna be taking you through payments hub starting with the overview screen. The payments hub overview screen brings together summary payment activity across all of your payment gateways and payment methods where you're transacting. The screen consists of a number of summary cards starting with global payment volume distribution on the left side. This is a heat map showing you where your payment volume is coming from by country with the highest volume country in the darkest color. On the right, payment method distribution shows you the distribution of transactions starting with the most and leading to the least popular payment method. Further down on the screen, we have a number of summary cards. The first three cards along the top here are your success rate. And success rate is essentially the inverse of a decline rate or a 100% minus whatever your decline rate is. We have a blended rate for your overall success, and that is further broken out into CITs and MITs. And if you're unfamiliar with these terms, CIT stands for a customer initiated transaction. These would include sign up transactions as well as customers making item purchases or customers coming into your checkout or account management pages from Dunning to update their payment methods and check out again. These are all payment methods where the customer is in session on one of your pages. MITs or merchant initiated transactions are just what the name implies. These are automated transactions that are generated by Recurly. These could also be transactions that you, as a merchant, create on your customer's behalf inside of the Recurly admin dashboard. The three cards along the bottom summarize Recurly's value added services. These include, account updater, and what you see here in the leftmost card is the number of successful or the volume of successful transactions that occur on cards that Recurly has updated at some point in the past. Next up, we have payment retry recovered revenue. This includes all revenue that succeeded on a subsequent transaction where the transaction failed initially. So this is showing Recurly's intelligent retries and a number of other recovery methods coming together to provide revenue lift. The final card in the right, if you're a merchant using, count anti fraud protection, this is showing you how many transactions were blocked in the time period. And for these cards along the bottom, if you do not have this feature enabled in your site, you will see a promotional message and a call to action with a link where you can click to learn more inside of Recurly docs. And that summarizes all of the features inside of the payments overview dashboard. And I'm gonna thank Jeff for recording this so you guys didn't have overexposure to my voice. Jeff definitely has a more pleasant voice to listen to. So thank you, Jeff, for being the audio on that as well as the walk through. I wanna start really quickly just saying, why did we do this? What are we supposed to do with this data? Well, what this does, it gives better insight into when you see a customer initiated transaction. That's generally a new sign up versus a merchant initiated transaction. We hadn't previously had visual breakdowns of where your success rates were, where your declines were coming from. And what this does is helps inform, should we be talking about x, y, or z approach to improving those rates? Ultimate goal is obviously as close to a 100% as we can get on those success rates. 100% never gonna be perfectly acceptable or reasonable to expect. But what we want is to close that delta and understand first where that delta is coming from. So we did get a question, our first question, and it is related to this first set of dashboards in the overview. So, Jeff, are recurring payments MIT? Yes, Patrick. They are. Recurring transactions predominantly are gonna be MIT transactions. They're gonna be the bulk of your MITs. Again, MITs are anything where the merchant initiates, so it's an automated transaction. The customer is not in session, so it's gonna be all of your subscription renewal payments. And in rare instances, some merchants may go in and do, a purchase on a customer's behalf inside of Recurly Admin. Those would be counted as well. But overwhelmingly, MITs are your recurring transactions. Excellent. Let's, let's go ahead and advance to our next dashboard. Alright. Thanks, Patrick. The payment processing dashboard, this one's a lot more detailed, and it provides a lot of granular breakout detail by, payment method gateways, individual card bins, as well as surfacing the top decline reasons for why payments are failing. Let's go ahead and start the video, and we can walk through this. Next up, we have the payment processing dashboard inside of payments hub. This dashboard provides, payment success rate and payment decline rate details in much greater detail. It's broken out in a number of different ways. But starting at the top, it leads with your overall success rate, and that's further broken out by success rate on individual days. Moving down the screen, we have payment method distribution. This is showing all of the transactions that were attempted and succeeded for individual payment methods along with, the success rate for each. And these columns are sortable. I can click on any of these columns and sort them to see the overall success rate. And as you can see here, PayPal is the healthiest payment method followed by Venmo, Amazon Pay, Google Pay, and then moving into cards. To the right, we see overall gateway success rate. So this is an indicator of, gateway health. And then down below, we have, card bin success rate. So this is looking at cards by their bins or their first six digits. And here we show their transaction count, successful transactions, and percent as well. And if I wanted to look in here just in terms of, like, which of the card bins where we're seeing the most activity, I'm gonna go ahead and click on that. This may take a little bit of, time. There's a quite a few, card bins in here. And while this is loading, there we go. So we see the highest volume card bin with a 111,000 transactions, 56% of which were successful. If I hover on any of these lines, we will show you the card metadata that we currently has on file, including, who the issuer were was the card brand, the card level, all of those types of details. Moving down to the last module on the page, we provide a tally of the top payment decline reasons, and these are organized around recurly's description for each type of payment failure. As the individual gateways have their own codes and descriptions, we normalize these together into a unified recurly view. We also let you know whether these declines were soft or hard declines or fraud. Hard declines are not retriable. Soft declines are. So that's another piece of valuable information. And then we also show you the transaction count here. As you can see, insufficient funds are, the leading decline reason, and that summarizes payment processing. Thank you again. One thing I neglected to call out in our first, video here is filters. So you have filters available at the top as well as as Jeff demonstrated in the video. When you click on, some of the values, they will also allow you to filter. So I do wanna make sure I call that out for everybody so that you do know that they are available to be filtered down. We have a few more questions, Jeff. Are you ready? I am. Hit me. Alright. I did respond with the glossary of terms. So we do have our glossary of terms posted as well. So let's move to the next question. Can we see somewhere successful and fill your payment ratio by invoice versus all attempts? We don't have it by invoice, but we definitely have breakouts by attempts. And when we get to the retry dashboard, that might help answer that question. And I'll point out this is something we have available in our, custom reporting. Not every merchant will have access to custom reporting yet. I wanna say yet. However, this is something we can show. All of my customers are in The US, Jeff. Can we filter by state? You can't yet, but that is certainly a great enhancement request. This is a good call out. I think, Patrick, you're gonna mention this later. We are gonna be adding app queue prompts to all of these dashboard pages, so there will be a place where you can submit fee, feature requests directly from the dashboards. But, yes, for US customers, we can certainly look at providing a US centric view that allows you to drill down by state. It's a great suggestion. And for those with analytic access, which you will require in order to see the payments hub at all, we do show a heat map by state if you go into your recurring billing and then your billings regional will show by state. So it's not gonna have all the same datasets and data filters, but it will show you a little bit better heat map of your states. So I wanna point out we have some of it, but it is still a work in progress for getting everything broken down in every way here through the payments hub. Still growing. I'm not sure I understand this next question, but maybe you do, Jeff, is for the thing. Can we see financial details when exporting? And maybe, Laura, if you wanna elaborate on what you would wanna see, you can put that in the chat. So we will wait for Laura to elaborate on that one. Top failure reason is none. What does that mean? That actually could indicate a technical issue where we're actually something is causing the payment to fail before it's processed through the gateway, and so we're not getting a gateway response. That's definitely something that we would want to, investigate further. And so that's something I would actually flag and raise a support ticket for us, and we'll definitely look into it. Alright. We got a response from Laura here. Mostly the bank names so we can see if the group of bins isn't doing well. That's in fact man, I wish I had planted that exact question, Laura, because this is part of what you get when you hover over that. And, yes, when you click download, this does actually, export as part of your downloads. Alright. Let's move on to our next dashboard. Alright. So let's talk about account updater. Again, account updater is one of those value add services. Not all merchants may have this available. So, if you don't, you will not see this in your left side nav, but anybody who has AccountUpdater enabled will see this. Let's go ahead and start the video and walk through the dashboard. The next dashboard I wanna show you is account updater. This is a pretty simple dashboard, but it's got some pretty powerful information in here. For merchants that have account updater enabled, you will see this dashboard. And the two key metrics that it tracks are successful card updates. So it's tracking how many cards were updated in the time period as well as the amount of payment volume that was processed on those updated cards. So card updates are updates that actually happen in this time period. Payments authorized on updated cards also is the payment volume generated on those cards in this time period, but those cards could have been updated at any point in the past. So this is successful transactions on updated cards. Finally, down below, we show a breakout of the individual update types. This can include, expiration date updates as well as a full card replacement where we've updated the number on the card. Looking on the right, we have updates by card type. As you can see here, Mastercard is the most popular card type with the most updates. Then we have Visa and Discover and AmEx. And even though we have a small number of updates on these, this is still useful. If this number were ever to drop to zero, it would indicate that there might be some kind of technical fault that needs to be investigated as that, card brand may have stopped updated for some reason. Oh, my favorite, the card updater. So account updater, I wanna point out, has two different mechanisms here, and you'll see those both called up on the called out on the update type. We have expiration updates and card updates. Expiration updates are somebody who, for example, signed up with a card that was gonna expire at some point during your, subscription life cycle. So let's say I signed up in December 2025. My next billing period is June 2026. But in May, my card got a new expiration date. That would go under account updater. Recurly has direct relationships with a lot of these brands to be able to pull those updates and allow expired card forwarding. Now let's use a real life example of Patrick being Patrick and, yes, let's say I left my Discover card on the table at an Applebee's in Miami, Florida. I still have the same Discover account that I've had for twenty five years. I have a new card, though. It's got a new card number. It has a new CVV and a new expiration date. But, again, linked to the same account, that would be account updater is when a new card has been issued against the existing account. So, yeah, don't leave your card on the table in Applebee's. In fact, I would say go to better places than I go. Alright. We have a few more questions. Let's see here. Can we add AI on top of this where we can submit a plain text. I will go ahead and steal this one from you if you don't mind, Jeff. We. Sure. do actually this is still an early access right now that Recurly is building out. So it is limited availability, but we do have public MCP becoming available. We don't wanna say a date, so I'm gonna shut my mouth so I don't get in trouble. But it is in our lands. Yes. And without without promising too much, Recurly is very much an AI centric company. You're gonna see a lot more AI enhancements layered on top of, analytics in general, to really move more towards question and prompt based querying of the data as opposed to just, I need to know what the filters are and run a query and that kind of thing. So more to I'm gonna hang. on to one of these other questions because we will cover it. The term glossary we'll go ahead and put the term glossary in the chat for you, Wendy. What does BIN stand for, Jeff? That stands for a bank issuer number. So every, issuing bank and even sub card brand has, essentially a six to an eight digit number that is the leading number on the card. Like, if you were to look at, like, all Chase Sapphire cards that are issued by Chase Bank, they all have the same first six digits. That's what identifies the card, whether it's debit or credit. It's how things like Apple Pay and Google Pay render the card art on, like, your phone and your watch and that kind of thing. But it's it's basically the organizational system around which, all of these card numbers are identified by who the issuer is. And we can rock, paper, scissors the next one, but will you be adding data for when account updater fails to understand You want me to take that one? we could. We we do have access to it, and there are some interesting reasons for why it it it fails. We have internal diagnostic dashboards for this, but it's really it's really a lot of noise. You know, it's things like the bank is not participating, so they can't provide. It's more of those types of things. And we just at least kind of like to make this first version of the dashboard simple and accessible, chose not to put a lot of that low level diagnostic data in this in this first Thank you. And in respect to time, we're gonna move to our next dashboard. release. Alright. So, let's talk about, the payment retry recovery dashboard. This one is pretty complex, and I I did a kinda slow video on this one. So what I'd like to do is just, like, let the video play. I'm sure this is the one where people are gonna have a lot of questions. So maybe Patrick will will play the video, and we'll break the two question rule on this one and take a few before we move on to the next one. So let's start the video. Now let's look at the payment retry recovery dashboard. This is one of the more complex dashboards. And because we have other dashboards for Dunning that are part of our core analytics, I wanna walk through this one slowly as it takes a more payment centric view of recovery. Starting on the top, we have recovered transactions. So these are transactions that initially failed at some point but have now succeeded on one of their future payment attempts. These are transactions that succeeded during the time period. So we have 17,626 transactions. And then over to the right, we have, breakout details of how many of those transactions, succeeded over the time period that's in view. Down below, we have a number of summary cards. The first of which is retry attempts. So these were all of the retries that were attempted during the time period or subsequent transactions after the initial failure that were tried. And so if you compare these two numbers, you'll see it took us a little over a 150,000 payment attempts to get a little over 17,000 actual succeeding transactions. Moving to the right, we have revenue at risk, and this is the volume of any invoices that failed on their first payment in this time period and went into Dunning. This is really important because, this number represents the initial transaction failure. If you look at the Dunning report, the Dunning Dunning report shows things that actually went into Dunning, and this is actually counting those transactions before that happens. So this number might be a little bit larger if you're comparing these two dashboards to each other. The number to the right is payment retry recovered revenue. This is the total payment volume of all of those transactions that succeeded in this time period. So if you look at both of these numbers, revenue at risk is anything that initially fails in the time period. Revenue that's recovered is anything that succeeds in this time period. And these two numbers aren't necessarily connected together. The revenue at risk might represent revenue that is recovered in the future after this current time period, and the the retry recovered revenue could represent a successful payment for something that failed prior to the start of this time period. So what you're ultimately looking at is a trending view of what's failing and what's succeeding. And if you compare these two numbers together, you'll get an overall recovery rate, which for this merchant is a little over 40%. The other graph that's new in the recovery dashboard is showing when the successful payments happen relative to how many tries it took to get a successful payment. And this is really an interesting graph because here is where you can see the power of intelligent retries and, other recovery methods working together to produce a positive result. Shockingly, no new questions, but I will elaborate on a couple of things. here. I will point out here recover or sorry. Number of retries. There is a limitation by some card brands that we are not allowed to retry a card more than 15 or sorry. The same invoice on a card. More than 15 times in a one month period. So anybody with more than 15 retries on that either manually retried it or, that was longer than a one month dunning period. So it did enter a second phase of retries. So I wanna point that out is that's a limitation not placed by Recurly, but placed by some of the card brands that we make sure that we don't get you into any sort of trouble on that. We do have a question here. Does retry recovery include customer updates? And are there any plans to include the source of the retry in the dashboards? You want me to I can take that. and keep it keep it short and sweet. Yes and yes. So it it includes all the possible ways in which a payment can succeed. So if a comp customer is clicking through on a Dunning email, they're coming back into session, they're updating the payment method, and that's what results in the payment being successful, you know, that could be on, like, attempt eight after seven intelligent retries failed just because, you know, the card which is bad and it's never gonna work. So it could be that. It could also be, for for some partners that are using, Indicia as, like, a, kind of, like, collector of last resort type of situation. It includes all of those. It also includes, any manual posts that you do as well. So it includes all those things. So, the natural thing, and I will just, you know, take you take you at your suggestion. The one thing that is missing here that is in the Dunning dashboard that I do think we need to add here is breakout detail on, what created that success. So that's, like, an obvious omission here. And so we we definitely will be adding that at some point. Thank you. And I will call out another thing. And that fluctuation in the recovered transactions is we do have an intelligent learning model that does push these retries so that we aren't just pounding retries on the first fifteen days and then you never recover it. So it's a machine learning model that is constantly evolving. The reason you'll see some of those fluctuations is sometimes that one's just gonna fall on a Friday that was a payday and you're gonna get a lot more out of those. Sometimes it's gonna fall on the fifteenth of the month. Again, a common payday. And other times, it's gonna fall on the ninth on a Tuesday because that was when it was trying to retry to see if that is a source of success. So we do our best to not incur gateway fees for you, and we do always keep evolving that model. Yeah. I think just. to further that a little bit just to get into how the sausage is made, you know, really there's really two two levers here. One is, Patrick, like you say, there's the compliance aspect of it of how many times can we retry for a given card type or an APM. They all have different compliance rules. There's penalties if you don't follow those rules. That kind of, like, defines the automatic side of it. The secret sauce for intelligent retries is using, ML model to essentially shift the clock to ultimately decide when is the best time to do the next retry that is both compliant and has the optimal chance of success. And that's why you see kind of the spikiness in the data day over day. Yep. And also on that bottom line, you'll always notice a down into the right trend as there are less invoices available as more have been recovered along the duration of those retries. Alright. Let's move on to our next dashboard Alright. here. This is this is the last one in the series. This is the fraud prevention dashboard. This is for any merchant who has, count enabled. Let's go ahead and roll the video and walk through it. Okay. The last dashboard I wanna show you today is the fraud prevention dashboard within payments hub. This is an optional dashboard. You will only have availability of this dashboard if you have integrated count fraud protection on your Recurly site. If you do, you will see this screen available in the left side navigation. So let's walk through fraud prevention for this merchant who is using count. There are two key numbers that this dashboard tracks. The first of which is blocked transactions. So these are transactions that were blocked as fraudulent by count, and we show a summary count for the time period as well as a daily count over time. We also show an average risk score, so we can see how this is trending. And count three sixty uses counts omniscore. It works just like, credit ratings. Good numbers or high numbers tend to be good or low risk. Low numbers tend to be bad or high risk. The other thing we show here, and this is new in our count three sixty integration, is we support fraud prevention with count beyond just credit cards now. So we now support all of the payment methods that are available and supported in Recurly's API as well as RJS. And for this merchant, you can see that they have got some fraud blocks across cards, Google Pay, Apple Pay, and a tiny bit of fraud on, PayPal and Venmo as well. To the right, we will also show block transactions by gateway. For this particular merchant, they are only using, the Braintree gateway. So this is the only gateway that we see for this merchant. But if you had more gateways in your site and you were seeing count, you would see individual breakout details by gateway of how many transactions count is blocking. I feel like I need to do a back to the future doc brown reentry. Marty, we're back at some point here. So we are back in our live form here. Jeff, we have a question. What period does the versus compare to? That's a great question. Probably should have covered that right up front in terms of how all these dashboards work. But put it simply, the prior comparison period is the immediate same time period just before. So if your if your current view is a week, it'll be the prior week. If it's trailing thirty days, it will be the thirty days before that. It's just matching the same like for like time period. Perfect. And, you know, you actually cued me into something I if we mentioned it, I missed it. But perhaps we should call out these being new dashboards. When you set your filters, the default filter is thirty days. The default filter is yes. yes. Not all of these have long historical datasets as they are, I think the word is new. Yeah. So they will have building longer and longer datasets as we go. But for now, Jeff, do you know off the top of your head the longest that we can filter to at the moment? Well, for some data, you can filter back quite some time, but there is some data that's unique to payments hub that was just instrumented recently. So things like CIT versus MIT flags on the data. We started tracking, all of the enhanced data that payments hub uses as of January 15. So depending on how far you go back, some some cards on some dashboards may not render if you go back prior to January 15. Thank you. I don't see any other fraud related questions, though I did see one pop up in the chat that I now naturally can't find earlier, and I said I would refer back to it. But somebody had asked, what about fraud related information? And that's why I said I would wait for it because we would cover it now, and here it is. Delivered as promised. You were the one that I was waiting on, whomever you are. I apologize. I can't find it in the chat. Do we have any other questions? I'm gonna give everyone a couple of minutes here, a couple of seconds here. Yeah. I'm, gonna do the Jeopardy I do. sound. I people did have a few additional questions around account updater, and there's one really important one that I wanna call out. There's a question in here. Now that Capital One has acquired Discover and is converting their Visa, Mastercard card holders, to the Discover network, will AccountUpdater catch these migrations? And it will. So AccountUpdater, will handle these sort of cross card brand updates where, you know, the customer may have started on a Mastercard and they're now getting a reissued card that's that's that's coming on Discover, we will handle that case and update the card in place. Not only update the card, but update its brand as well. Thank you. And we have another I wanna get to here. Curious why I would care about success and failure by bin. What action would I take with this data? Well, there's not a lot of action you can take with it now, but this is maybe a teaser of some some future things that Recurly is working on. I know I've been in a lot of, conversations with merchants recently. So Ben identifies the, the type of the card. And one of the things that's really interesting and that we see some urgency particularly is they might see an initial high sign up rate. You know, CIT is a great, MIT is not so great. And the reasoning behind that is if you look at the bins that have the low success rates, they tend to be prepaid debit cards that run out of money or, virtual cards that, like, you know, might be controlled use, single use, those types of things. If you can organize and map around those bins, then the you know, I I don't wanna make immediate promises for delivery in a timeline, but one of the obvious things that you would wanna do is block bins that you know to be potentially unhealthy in a recurring situation. Just just don't allow people to use them to sign up for a subscription. So that's that's that's why this data would be important. I'm gonna go ahead and add another one, which I came across literally last night. So if we'd done this twenty four hour previous, I wouldn't had this context. And that is we came to find out that one of our merchants had high declines coming from a certain region, and that region has strict rules about interchange. And that was reason that now we should be discussing expansions into localized payments and localized currencies into a specific region. So by having that bin data, we were able to expose the region that it's coming from, how common that is, the declines, and we were able to peel back those layers of the onion. And now we have a reason with data instead of just we recommend, but rather showing you have x amount of people that want to sign up here, but you're not giving them the opportunity to. So it really helps you chase after some additional revenue with the right tools using the right data. So that's a new one for me, and I wanted to make sure I shared that that is another potential use for the BIN. We did find the question about fraud. And that is, what are the most effective signals or analytic approaches to detecting card testing and fraud concentrated on specific things? Do you wanna take this or me? I'll take a first stab at it because I think this is where, you know, platforms like Count three sixty really add their value because, you know, if you know anything about the dark web and how this works and people doing card testing, they're buying these cards in, you know, they're buying these cards in bulk and they're testing them in bulk. So you're you're looking at things like velocity. Is it how many how many transaction attempts are coming? How quickly? Are they all coming from the same IP? Does does the does the shape of the environment data make it look like it might be the same computer or pools of computers. And that's where really count can really shine because it can use its ML models and its data to ultimately say, this is a bad actor. We've seen this person before, or this looks suspicious. We're gonna down rate it because of, you know, all sorts of things like garbage email addresses and things like that. This is this is really where platforms like count show their value. Yeah. And there's a couple of other things I wanna point out as well. And one of those is the gateways will identify as will the card brands. They will identify things like velocity testing and automatically decline those if they see velocity testing taking place. So they will flag those, and you will see then some of those higher decline rates. Higher decline rates aren't always a bad thing and sometimes be a good thing because it's saving you from a fraud attack. And how do you distinguish between there's there's all sorts of fraud rules on that that can be set as Jeff said. In things like count three sixty, you can set those fraud rules of certain regions can be blocked or certain BIN sequences can be blocked. I have several merchants that, for example, determine that prepaid BINs are incompatible with their subscription model. So they don't want reloadable or sorry, non reloadable prepaid bins to be allowed at time of purchase. So all sorts of things that you can do with that to identify what might be a pattern versus a genuine customer. We can have a whole webinar just on that. And let me check if we have any new ones coming in here. No. I think that is it for questions that have come through here. I wanna hand this back to Ashley for oh, wait. Woah. Woah. Woah. Woah. Woah. Naturally, when I say that, it's blowing up. Let's slow down the train here for a second. I apparently inspired everyone's questions to be asked, and I appreciate all of you for asking. We're gonna go ahead and move this one. And when a card is entered initially, is there a way to identify it as prepaid before it's run? Yes. This is a filter that count allows, and many of the gateways will allow bin filtering as well. Yeah. I think the specific question is, like, right now, it's like you could do it through count, so count could stop it before the authorization attempt happens at the gateway. But this is a you're not you're not the first person to ask for this, and it's definitely something that we're looking at. And I think what you're really asking for is the gold standard is if you know it's a blocked card, tell the customer as they're typing it in. It's definitely a challenge because PCI scope is involved there. So kind of like how you do that, but it's an interesting challenge. And I don't wanna make any promises, but I'll just say you're not the first to ask for this. I'll just leave it at that. Does Recurly provide any data on success rate benchmarks? What is a good and bad success rate? Pat Patrick, I think that's one I would say probably take that up with your CSM given that, like, it would be very hard for us at a dashboard level to say, you know, we've got merchants with different MCC codes. They're in different industries. Some merchants are more high risk and low risk. So, really, it's it's kind of like your your CSM is the best person to ask this question to because they can they know best in terms of, like, like for like and can give you kind of, like, more of a cohort readout, if you will. I appreciate that. We are here for a reason as CSMs. And we do watch your specific account information. So like you had called out, Jeff, things like MCC code changes, gateway changes. If you've added alternative payment methods or any of those sorts of changes, we wanna make sure we monitor impacts for, and we're advising you in real time on those. So there isn't really a benchmark. It would be very difficult to create a benchmark of success. One of the most common soft decline reasons is insufficient funds. How do we make your customers have more funds? That's a very difficult one when they aren't on my payroll. See here. How can we access the fraud prevention tool if it's not shown on our payment hub. So you would have to enable that. That's under your configuration in Recurly app, and you would have to have admin permissions to Recurly. It's under configuration, and there is a tab called fraud management. What specifically is a gateway error? This is a great one. And how can it be minimized or resolved? Gateway errors are, essentially a technical fault within the gateway. So the gateway, for some reason, was unable to, you know, respond or it was wasn't able to reach the network or something like that. So we do have something called, a gateway failover capability. And, you know, for those types of errors, we do have the ability to failover to an alternative backup gateway. And if that's something that you're interested in, definitely take that up with your CSM. They can give you some help, some advice on, like, who you might wanna use as a secondary gateway. Again, if the gateway just returns some kind of a technical fault, we do have the ability to do an immediate retry on a secondary gateway. Perfect. This is more of follow-up feedback as opposed to really a question, but we'll go ahead and share that. On the pin question, it would be helpful to show card type. We do have that available on the hover. I don't believe that's yet available on the export. Is that correct, Jeff? Yeah. I mean, this this is top of mind in terms of make it filterable, displayed in the data grid, maybe give that card more space so that you can see Chase, Wells Fargo, Sutton, whoever, Visa, Mastercard, more of that breakout detail. Like, we have it. I I think what Ed and I was asking for is just make that discoverable, make it reportable, make it the entry point as opposed to hiding it over like a hover pop up. It's in it's in the top of the improvements list. That's what I'll say. Hey, Excellent. guys. Ashley has rejoined us on the stage, so, Ashley, I'm gonna hand in the hook, back off to you. we're at time. This was fantastic. Oh my gosh. We have so many questions still unanswered, which I feel really bad about. But I just wanted to have a a moment to jump on and let everyone know if we didn't get to your question live here, we will reach out to you and answer your question, via email. You'll hear from me, or from Santi. He's probably got his mouth wide open being voluntold to do something all of a sudden. So but we will reach out to you. Thank you for all of your questions. Guys, are you cool for me to go ahead and wrap up, or do you have any closing thoughts before we move forward? I was going to call attention to the chat. You may notice couple of resources in the chat. Ashley, did you want to discuss what those are? Absolutely. So I don't know why my resource slide is grayed out on my screen. Is it gray for everybody else too? No. It's good. We can see it. are. good. That works. Okay. So if you look over in the docs panel between chat and q and a, you'll see quite a few links there. First of all, this slide deck, which has all of these demo videos linked in it. Also, the learning path that we shared with you, this week, some of you got it upon comp like, your confirmation email, and some of you got it after you registered. That walks you through this payment hub with a few activities on using your filters and just some additional information. We'll also update that with these demo videos as well. So you have the full learning path there for you anytime you need to return to it. Also, we had quite a few questions that were answered with contact your CSM. I know a lot of our navigate merchants don't necessarily have an assigned CSM, but we hold, global office hours with our CSMs for that purpose. So there is a global office hours or CSM global office hours link there. We offer that once a week at different times and dates. So find what's most convenient for you, jump on there, and that's where it's it's a great place to bring those questions questions about your specific data, about your account, or any questions that you have that you need answered pretty quickly. Also, I'm not sure, Jeff, if you mentioned this, but won't we would be collecting feedback for these dashboards in app? We will. We'll be launching an AppQ prompt on all of the dashboard pages. It's not there yet. It will be soon, but there'll be an opportunity for you to give us feedback. Yes. Yes. And we always want to hear your feedback. We We constantly iterate and constantly do what we can to make this experience make this work best for you. So and this was, this dashboard was built on merchant ideas. Am I correct? This was requested. Yeah. So thank you. so. Alright. I think we have thirteen seconds left, so I'm gonna hurry up. Guys, you are amazing. This was fantastic. Thank you so so much for doing this with us today, and thank you to everyone who attended. I mean, it was a lot of fun. This was a very busy, engaged webinar. We really, really appreciate your time here. Thank you all. And. one last call out, there is a link. If you enjoyed this, please leave us a review or any feedback. Please leave us a review in g two. You get a an Amazon gift card because it is a it it it's a special special review. We really take those seriously and appreciate you. Thank you. Thank you all for your time and attention today. Yeah. Yeah. Thanks. Alright, See. you all. Have a nice day. Bye.