Trusted Digital Transactions with Adobe Acrobat Sign and OneID

Transcript

Let’s go ahead and get started with this webinar. Welcome everyone. We’ve got a bunch of you that have already joined the room. We’re excited to go through this content and share this content with you today. Let’s go to the next slide, please.

Great. Here is who you will be hearing from today. We have a good team of presenters from both Adobe and OneID. Let me quickly introduce everyone from left to right. My name is Dave Stromfeld. I am a Principal Product Manager on Adobe Acrobat Sign. I will moderate this webinar today. I’ve been at Adobe over 20 years in a range of roles, now exclusively on Adobe Acrobat Sign, and really excited to share with you today all of the great content that we’re going to share with you. I’m joined by some others. Andrei, you want to go ahead and introduce yourself? You’re on mute, Andrea. Can you unmute? Thank you, David, and thanks everyone for joining. I’m Andrea Valle, Principal Product Manager for Acrobat Sign. I focus on security, digital identity, and digital signature, and I’m one of the presenters today.

From OneID, we have Keith. You want to introduce yourself, Keith? Yes. Thank you so much. My name is Keith Mabbitt. I’m the Chief Commercial Officer with OneID.

Thank you so much for the opportunity to come and join forces of Adobe today.

It’s been a relationship that we’ve been working together for several years, so looking forward to sharing with people. Thank you.

Great. Elliot.

Good afternoon. Elliot Howard from OneID, working alongside Keith, responsible for some of our most strategic partnerships, including OneID, and I echo everything that Keith said.

Great. Thank you. Let’s go to the next slide, please.

This will be our agenda today. We’ll spend a few minutes right now giving you an introduction on how the webinar works, and then we will move into an industry and market overview. We’ll give you a really good deep summary of what is the Adobe and OneID solution, and then we’re going to leave you some resources and next steps, and we will leave some time at the end for questions and answers.

We can go to the next slide.

Just an overview of the webinar. If you face any technical issues, usually if you have an audio issue or a video issue, usually the quickest solution is just to close your Microsoft Teams window and then rejoin the webinar that usually resolves the issue in almost all of the cases. But not to worry, we are recording this, and so you’re welcome to take screenshots. We’ll knock things down as we go, but you will be getting an e-mail after this webinar with a full recording of the webinar and some of the key links that we’re going to share with you today. If you don’t want to take notes or take screenshots, then you will be getting everything in your e-mail inbox afterwards.

Question. One of the buttons at the top of your toolbar is a Q&A button. If you open that, you will open our Q&A pod, and that’s where we’re going to be encouraging you to ask questions. We have a few people standing by to answer those questions. We’ll get to as many of those questions as we can as they come in in our Q&A pod. If you see someone ask a question that you like, please upvote it. Then at the end for the Q&A portion, for those questions that we couldn’t answer, we’ll do our best to pick out a few questions from the question and answer pod and answer those verbally at the end of the webinar. So we encourage you to ask questions, upvote questions, and we’ll get to as many of those as we can during the webinar. Finally, we are going to be using polls and surveys during this webinar to gather some feedback from you just so we get a pulse check of what you’re thinking and what your interests are. So let’s go ahead and go to the next slide.

Let me go ahead and launch our first poll here. Let me bring that up on the screen. You should see that on your screen right now, and this is a two-part poll question. The first part is, how familiar are you with identity verification? Then if you click that next arrow in the lower right, you’ll get a second question where we’re interested in where you are joining us from today.

So I see some results coming in.

This is great. So far, the majority of you are not very familiar with identity verification. So this webinar is going to be a great overview for you of exactly what it is, and why you might want to consider using it in your organization, using Acrobat Sign and OneID going forward.

As expected, we have most of you joining us from the UK and Europe, and then we do have a portion of you that are joining us from North America as well, as well as some other places, so that’s great. So go ahead and close that poll when you’re done. You can click the X in the upper right, and let’s move on to the next slide.

I think at this point, Elliot, I’m handing it off to you.

Perfect. So I thought, as always, it would be good to start with just a very quick overview on what’s happening out there in the world.

Everything happens for a reason, and so understanding the external factors is important. Let’s move to the next slide, please, Andrea.

So we’re all familiar with Acrobat Sign or alternatives. We’ve all been using them for a long while now, so we will all be aware of how transformative digital signing has been for both the corporate and the consumer in terms of cost efficiency, experience, regulatory compliance.

As we’ll have all seen from some of the announcements this week and of late, the regulations are changing and moving at what appears to be a significant pace now, and that’s creating a gap in most signing workflows that’s becoming harder and harder to ignore.

Email and SMS authentication only proves that someone has received a link from your signing process. It does not prove who they are, and as the regulation firms up and the requirements continue to get tighter and tighter, that distinction matters enormously, particularly when you’re executing employment contracts, financial agreements, non-disclosure agreements, or any regulated documents.

We’re all aware of AI.

62% of organizations have experienced a deepfake attack in the prior 12 months from today, and that’s a statistic that comes from Gartner. So deepfakes are no longer a future threat. They’re happening now. They’re happening to businesses like ours, and Gartner surveyed over 300 cybersecurity leaders, and who all reported that 62% number. So this is a very significant number that’s being scrutinized at senior C-level and board level within a lot of organizations.

There’s been a 5% increase in dedicated AI-generated document fraud between April and December 2025.

AI tools have made document fraud extremely easy. In fact, we would say trivially easy. Bank statements, pay stubs, onboarding forms, any kind of document you can think about, the documents that you’ll sign, workflows, process daily are being targeted and forged.

30% of enterprises will no longer consider stand-alone identity verification reliable. So the forward warning from Gartner that they’ve made in 2026 is aimed directly at organizations using email, SMS-only signing off authentication. That includes most Acrobat sign accounts today and most of the alternative sign products that are out there.

The good news is that Adobe, along with 1ID, has already built the infrastructure and invested in the solution to solve this. The digital identity gateway in Acrobat sign is designed exactly for this purpose, and 1ID is a certified identity provider within that gateway that plugs straight in. So during this webinar, Andrea and I will show you what that means in practice, how to use it and how it benefits your customers.

Can we move to the next slide, please, Andrea? So why do we need to move and why do we need to move right now? There are two reasons that the timing matters. One, as I’ve mentioned, is regulatory and one is commercial, but both point to the same conclusion. Any organization that takes action now will be ahead of the curve, not scrambling to catch up with it.

So let’s just break this down from left to right. And as I said, there are two fundamental buckets. One is the regulatory pressure and one is the commercial urgency.

EIDAS 2.0, which will be coming into fruition November 2025, this is only five months away. The EU digital identity wallet goes live for all citizens and residents, and any counterparties that you may have in Europe will increasingly expect, and in some cases absolutely require, identity verified signatures, meaning email SMS is no longer fit for purpose.

If workflows aren’t ready, then we’re already seeing that compliance teams are putting internal pressure on the parts of the business that are releasing documents to understand what they need to do to get themselves up to scratch.

Ongoing GDPR enforcement.

The European Data Protection Board recently updated its guidance on electronic identification, specifically in late 2025.

The message from the regulators in the UK and on the continent is extremely clear. Signing workflows must demonstrate an evidence to who signed, not just that a signature was applied. Again, putting into question email and SMS authorisations.

And then the UK equivalent of EIDAS, for any of us with UK operations or based in the UK or with cross-border transactions coming into the UK, the expectation for advanced and qualified electronic signatures is already embedded in UK law. Email authentication alone doesn’t meet the bar for high value or regulated documents.

Then we move to the right, thinking about the commercial urgency.

This is the most powerful. There’s no rip and replace required here. There is no new platform to learn, no procurement process to run, no user retraining. OneID is already integrated and integrates as a certified identity provider within the Adobe infrastructure you already have. It’s a simple toggle button to get access to a step up from OTP or SMS or email.

It’s live today. This isn’t in beta or pilot or a roadmap promise. Adobe’s own 2026 release notes confirm verified form fields from OneID are production ready. They’ve been tested by a number of UK institutions and you can turn it on today.

The expectations have shifted. As I mentioned previously, your customers are expecting and consumers are expecting something different.

Some recent research shows that 80% of consumers expect stronger online safeguards. In the B2B world, the equivalent is counterparty due diligence. Procurement teams, legal functions and compliance officers are increasingly asking, how do you know who signed that? The question isn’t whether identity verified signing is coming. It is already here. The question is whether you get there ahead of the requirement or because of the requirement.

I’m going to hand over to Andrea to show you how we make this real. Andrea, over to you.

Oh, no, it’s time for a poll.

No problem. So, yeah, let me bring up our next polling question. And while I’m bringing that up, again, I will remind folks that the Q&A pod is available. Folks are standing by to answer your questions. So as you have questions during this webinar, please don’t be shy to fire those off and put those into the Q&A pod. Let me bring up our next poll.

Let me bring that up on your screen right now. So this is just a one-part poll. And the question here is how high of a priority is identity verification for your organization? So given what you learned, given what you researched or what you’ve discussed internally, how all are you thinking about identity verification within your organization? So please go ahead and answer that. I will leave that open for a couple of moments.

And it looks like for most of you who are answering the poll, it’s a high priority, which is great.

And then I think there’s a good percentage of you also that are still exploring and don’t yet quite have a priority, which makes total sense. So I’ll leave that open. So go ahead and answer that in the next three seconds. And then when you’re done, go ahead and close that. And Andrea, we can go ahead and move it to the next slide.

Okay.

Nice. Thank you, David. So up to this point, we have discussed the business problem and why identity verification is becoming critical. So now let’s have a look at what we mean when we talk about a trusted electronic signature. This will help you understand the powerful solution that Adobe and 1AD can provide together.

So a trusted signature is more than just a digital mark applied to a document. It combines the three important elements, the signature itself, the identity of the signer, and the evidence proving that identity. So let me walk through the diagram of this solution.

So at the center of Acrobat Sign approach, we have the Digital Identity Gateway or DIG.

That’s an integration layer that connects Acrobat Sign to a growing ecosystem of trusted identity providers.

Different organization and use cases have different requirements. Some need basic identity verification and other needs stronger assurance level to support compliance, regulated transactions, or internal governance requirements.

1AD is one of the identity providers available through the DIG framework. And through this integration, 1AD verifies the signer identity and returns trusted identity information directly into the signing process.

The result is a verified signature.

Not only do we know that a document was signed, but we can demonstrate who signed it, how they authenticated, and what evidence supports that identity claim.

So all of this evidence is captured in the signer identity report, which becomes part of the transaction record and can be retained for audit, compliance, and dispute to resolution purposes.

So now the question becomes, why is 1AD particularly interesting as an identity provider within this framework? So let’s look at that next. So Elliot, let me hand over to you again.

Thank you, Andrea. So why 1AD? So we’ve talked a bit about in my section and Andrea’s section is why identity verification matters and why it matters right now. Obviously, the next natural question is why 1AD specifically rather than another identity provider? So the first is we’re built for compliance, not bolted on, meaning 1AD isn’t a generic KYC tool that’s been retrofitted into Acrobat Sign. It’s a native identity provider within Adobe’s own Digital Identity Gateway or DIG. What this means is the verified identity data Adobe needs to satisfy EIDS 2.0 and KYC style audit requirements is already flowing through the integration Adobe has built and supports, meaning no middleware, no custom development.

The second point is it’s bank grade verification. We trust the banks with our salaries. We trust the banks with our mortgages. We believe that the banks should be entrusted with our identity. There’s no other identity verification method required. There’s no document upload mid journey. There’s no selfie live liveness checks mid journey that never work. There’s no new app to download.

And all of those, as we know, introduce drop off. Quite significant drop offs. At 1AD, we use your banking app that the signer already probably has open on their phone. It’s a familiar journey. It’s completed verification. There’s no behavior change required. It’s as easy as three clicks, three clicks and done.

It’s the broadest of all of the UK’s Digital Identity products. We reach, we believe, circa 50 million UK adults. That’s from the latest stats in terms of those that have online banking capabilities. And we already have five million wallets deployed out there for active service. What does that mean for you as a corporate user of Adobe Sign? Well, you can access broader signer populations, your customers, your employees, your suppliers. That reach means you’re not excluding anybody.

You’re not excluding people that don’t have access to a passport scanner, for example, or people who won’t do a selfie check.

And the good news for those returning wallet users, the journey is even simpler. Just log in, done.

So to summarize, 1AD gives you compliance grade identity verification delivered through the channel your signers already trust. And that combination is why it’s a firm favorite for the identity there within Acrobat Sign. And it’s not just an add on. And as I said previously, it’s already available. It’s already integrated. It’s as easy as flicking a toggle and you can get access to the capability and step up those OTPs or SMS or email authentication methods.

Back to you, Andrea.

Okay, thank you again, Elliot. So let me move to the next slide. So let’s now let’s look at some of the capabilities that Adobe has introduced to take advantage of this trusted identity information.

Up to this point, we have talked about the importance of verifying the signer identity. The next question is, how do you make that identity check more precise without making the workflow complicated? That is what this capability is about. So Acrobat Sign now lets administrators define the matching criteria for signer identity. So the organization can decide how strict the verification should be for a given use case. For some workflows, an email match may be enough, especially if email is used as a unique identifier in the identity provider space. For others, especially in regulated or high value transactions, you may want to require stronger matching, such as name-based validation as well. The important point is that this is configurable. You are not forcing every document through the same level of verification. You can align the identity check to the risk of the transaction. So, for example, if you are handling account opening, mortgage documentation, supplier onboarding or other sensitive agreements, you can apply stronger identity expectations to help ensure the signature comes with the intended recipient from the intended recipient. So this gives organizations a better balance of control, compliance and user experience, because the policy can be adapted to the workflow instead of the workload having to adapt to a rigid identity process.

And that leads us nicely into the next capability. Once you have verified the signer identity, how do you use that verified information to improve the actual form-filling experience? And if I had to pick up one recent capability that generated a very strong positive reaction from customers, this is probably it, verified form-fills. So think about the typical onboarding process. We ask users to verify who they are and then immediately we ask them to type the same information into a form, their name, address, date of birth or other personal details. That creates friction, introduces typing errors and increases the likelihood of incomplete or inaccurate submission.

So with verified form-fills, we have three simple steps. So step one, the signer first authenticates through the chosen identity provider, in our case, 1AD.

Step two, once the identity has been verified, Acrobat Sign automatically populates designated form-fills using the trusted identity information that has been returned by the provider.

The user does not have to re-enter information that has already been verified or provided by the identity provider. And then step three, Acrobat Sign doesn’t simply populate the fields. The signer identity report records, which values originated from verified identity data, provides additional transparency and auditability.

So from an implementation perspective, this is surprisingly simple. Works across Acrobat Sign authoring methods, including templates, API, text tags and the web authoring environment.

And administrators can simply use a standard naming convention to bind form-fills to verified identity articles.

The result is a better experience for signers, improved data quality, reduced operational effort and stronger confidence in information collected.

And now, rather than talking about it, let’s see it in action and we’ll work through the complete experience from both the sender and signer perspective.

So, first of all, in this screen you see the experience of the sender from a laptop computer. The user creates a new agreement by starting from a predefined template or by loading an existing document.

Then he wants to add recipients, which can be assigned to a specific role, typically, as in this case, a signer role. Then recipients are identified with their email address, also because typically Acrobat Sign engages with recipients via email notification. The next step is the recipient settings.

So it’s a section that provides the ability to configure behavior for each recipient. And that’s the interesting part of this demonstration. It’s the place where the sender can configure the authentication method to identify the recipient in a secure way. And as we scroll to the bottom of the list, we can see the Digital Identity Gateway section where 1AD is available.

After the selection is applied, then we can send the agreement out for signature. And then we have the next part, which is the signer experience on a mobile phone. So in this screen we see the user receives an email notification and by pressing the button they get into a screen where they are informed that they need to complete the identity verification using 1AD. And as this user named Claire clicks on the button, then the next step will be to perform the identity verification using bank verified data. So first of all, the next step will be for 1AD to inform the user about the request of consent so that her personal information is maintained under her strict control. And then the next step will be to inform Claire that she will have to log in to her bank to confirm her identity. So by pressing on the verify button, she continues and she will get to a list of banks. These banks are connected to the 1AD backend and after choosing the bank, she will be directed to her bank and login into that bank to prove their identity. So the screen will redirect to the bank itself and after a successful authentication, Claire will be informed about the data being shared. 1AD will then take over and depending on the business requirement, they may enrich the user’s personal information with indicators relating to identity fraud and regulatory checks, and will return this data back to Acrobat Sign. And then the next screen will be the preview of the agreement where the user can read and apply intent to sign and finally send the document back to the next recipient or to the sender.

So pretty straightforward. I think this is a good time for the next poll. David? Great. Thank you, Andrea. And again, just a reminder, if folks have questions or comments as they’re watching this webinar, please feel free to use the Q&A pod over the button at the top of your webinar window. Let me bring up our next polling question here. Let me launch that. It should show up on your screen right now. And so this one is which sign and 1AD capabilities are of most interest to your organization? So Andrea and Elliot walked through a number of capabilities of the combined sign and 1AD solution. And so which ones are speaking to you the most? And we’re getting responses come in. Looks like replacing one-time passwords and SMS is pretty high on the interest list. Identity checks is high on the interest list. But really a level of interest for all the capabilities. So let me leave that open for a couple more seconds. Please go ahead and submit your answers. When you’re done, you can go ahead and close that with the X. And let’s move on to the next slides, Andrea.

Sure. So before we wrap up, I want to leave you with the best starting point if you want to explore Acrobat Sign and 1AD more deeply. So let’s start with some Adobe Acrobat Sign resources. So if you are already an Acrobat Sign customer, the resources on this slide show you how to move from general signature use case to identity enabled workflows. You can start with the official learning hub and then move into the hands-on tutorial. And from there, explore the digital identity gateway, identity provider authentication, identity check policies in verified forms that we covered today.

Instead, if you’re not yet a customer and you are evaluating Acrobat Sign, then the 30-day free trial is the fastest way to get hands-on experience and see how these capabilities work in practice. The main message here for you is that we presented a set of capabilities you can learn, configure and pilot within Acrobat Sign directly with hands-on. So whether your goal is stronger identity assurance, better data quality or more trusted digital transactions, these resources give you a practical path to get started. And with that, I will hand over to Elliot to talk about some 1AD resources.

And just for folks, I did copy all of those links into the Q&A pod. So if you go to the Q&A pod, you should see all of those links available. You’re welcome to copy those and use those as appropriate. Elliot, go ahead. Thank you. So yeah, just building on Andrea’s point, a couple of links there. So you can learn more about 1AD and what we do. And the link is there and how we can help you improve your e-signing processes and experiences. We’ve also got access to a free trial product, which the link is there.

What we would like and encourage is that by working with Adobe, we identify some current workflows where you’re using maybe OTPs or SMS. And we can very quickly set up a live demo to give you real hands-on experience of how the 1AD via the Digital Identity Gateway can be a very credible alternative, a much more secure alternative for some of the methods you’re using today. So if that’s of interest, then please do let us know. But there are some more resources there that you can get access to to learn more about us. Back to you, David.

Great. So let me bring up our final poll. And let me launch this one right now. So this poll is about next steps. And it’s do you want to be contacted to learn more about the Adobe 1AD solution? So we are going to send you an email with a link to the recording and those links. So you have those available to you. But separately, are you interested in hearing more from Adobe and 1AD in particular about this solution? Have your questions answered and have a discussion on how we can help you move forward with what you’ve seen today. So if that’s of interest to you, please go ahead and click yes or no. And if you click yes, then we will be reaching out to you and talk with you about further next steps.

Let me see if we’re getting some responses. Yep, we’re getting some responses. And we’ve got some folks that are definitely interested in moving forward, which is great. So I will leave that open for a couple seconds and then we can move on to the wrap up. Or the Q&A, I should say. And again, if folks have questions that they have been thinking about that they want us to try to answer in our Q&A portion, please put those into the Q&A pod.

But let’s go ahead and you can close that poll. Actually, let’s go to the next slide, Andrea.

So this is a survey. You can scan that QR code. Let me put this link into the chat pod right now as we speak. So we’d really love your feedback on this webinar. What did you like? What could we have explained better? And also, what are some future webinar topics that you’d love to hear about from Adobe Acrobat Sign? So let me put that into the Q&A pod here.

There we go. So go ahead and scan that QR code or click the survey link that’s in the Q&A pod. And we’d love for you to, like I said, give us your feedback and we’ll definitely review that and take that into account as we plan for future webinars.

Let’s go to the next slide, Andrea. There we go. Q&A. So folks have been quiet. I don’t see many questions yet in the Q&A pod. We did get a couple of questions that came in separate from the webinar on this topic. And so Andrea and Elliot, let me just sort of bring you guys on stage here. Let me go ahead and ask these questions that folks had asked earlier related to sign and OneID and digital. So before you get into those questions, I see a question from Lorraine as an answer to your question. So the question is definitely for Elliot. So what would happen if the person bank is not listed when trying to verify their identity? So in the UK, we’ve got the majority of the high street banks. In Europe, we’re integrated with all of the national identity programs so they can use their country specific identity platform. For example, BankID in Sweden. Alternatively, we can then pivot them to a more traditional ID and V process with a document upload passport driving license.

But obviously, the user experience is best when they go through the bank verified journey.

I hope that answers the question.

I see a thumb up. So probably yes. Thank you, Lorraine, for asking the question. Yeah, I see a question from Jose for either Andrea or Elliot. Can this replace QES as the services provided by D-Trust? I think, oh, sorry, go ahead, Andrea.

Okay, yeah. QES, which stands for qualified electronic signature is a very specific form of electronic signature, which is highly regulated, both in the European Union and in the UK. So the key difference in the solution we have presented today is that digital identity gateway providers are not based on digital certificates as they are in QES. So the short answer is that if you are in a business for which a QES is prescribed, then this solution does not replace it because a QES is only as such if you have a qualified signature issued by a qualified trust service provider like D-Trust. But if you are not mandated to use a QES and you’re only looking for a high assurance electronic signature with a great user experience, then this can definitely be a replacement. Elliot, I don’t know if you want to add anything. Nothing to add. You answered it perfectly, Andrea.

Nice. Thank you. Let me, like I was saying earlier, let me ask a couple of questions that came in before the webinar. So the first question, Andrea and Elliot, is how easy is it for 1ID user to reuse the wallet in a new journey? Well, I think I covered this right at the beginning of the presentation. I mean, it’s easy, as you’ve seen, for three clicks using the bank login for the customer to identify and verify themselves. At the end of that journey, a wallet is created. Then the user then just uses their phone’s biometrics to log into that wallet because that wallet is then bound to the phone and the identity within the phone. And that’s it. Nothing needs to be done. We may need to re-consent because obviously the open banking regulations only allow us to keep the consent for 90 days. But within that 90 days, it’s as simple as holding the phone to your face and it’s done.

And Andrea, I think this other question that came in earlier may be for you. What is the key advantage of using 1ID versus phone authentication? Yeah, so the key difference is that phone authentication is definitely a very convenient authentication method because anyone with a mobile phone number can receive an OTP via SMS and therefore a very small user experience barrier. But at the same time, phone authentication is just pure authentication. It does not provide any identity verification. So if your business requirement is to ensure that your signer is exactly who you want to be and have a high assurance of the identity verification of the signer, then phone authentication does not provide that. It provides some evidence that someone having access to the phone was able to answer that. So we definitely need more higher assurance solutions like 1ID when you have a high risk business or where just the authenticating without identity verification is not enough. But functionally speaking, I mean, from the design of an Acrobat Sign workflow, switching from phone authentication to 1ID or other digital identity gateway providers is very simple. So from the recipient setting screen you have seen during the demo, you can just select one of the available services out of the dropdown list. And it’s exactly the same. The rest of it would be a specific user experience. As we have seen, 1ID based on bank verification, the user logs in into their bank to prove their identity. Other services use equivalent systems as also Elliot mentioned, can be an ID document verification, can be an agent video interview or very other systems.

Great. Okay, thank you. Let me see. I think a question just came in from Oliver. Is there a verification token that would be sent to the service provider for audit purposes? Yes, I can take it. That’s exactly what the Signer Identity Report does. Because essentially we collect the signed evidence coming from the identity provider, which is signed by the bank and we incorporating the Signer Identity Report for audit purposes. So this will be essentially the objective proof that the transaction occurred with the bank and therefore that all the data we obtained out of this transaction can be trusted because they are signed by the bank. So yeah, definitely yes, the verification token is collected and maintained for audit purposes.

Great. Okay, well I think that answers all of the questions that have been coming in. So could we go to the survey slide again, Andrea? So if folks didn’t get a chance to answer the survey, you can scan that QR code. It’s also in the Q&A. The link is in the Q&A pod, so you can click on the link. Again, like I said, we’d love to get your feedback. But at this point, I think we can go ahead and wrap up this webinar. Thank you, Andrea. Thank you, Elliot, for all your great information.

And everyone will get a link to the recording and the links. So I think we can wrap up here. Everyone have a great day and thank you for attending.