 Okay, I just want to discuss quickly how we use member ID inside of the C ledger member pass API In essence, we don't want to know From the C ledger side anything that is internal to your side. So we're looking for member ID to really to isolate Us from any knowledge of your system. So what this really means is you shouldn't provide a meaningful identifier as the member ID Pick a created correlation table or something in your system that ties the person To the member ID Just a simple table. We'll show you an example in a second giving ideas things. We don't want pushed in Things like Social Security number a member number. I'm an account number if you're using CU FX party ID These are all unique and in special to your system. They're important to your core and your ancillary systems Giving idea. Here's just a quick example. If you look on the right hand side here I've got a member ID. It's just a grid just randomly created And on the left hand side, I got two different systems on the core side We have a member number of three four five four three two and there's an auto loan ancillary system where it's The user ID is something like auto two three four four five We would correlate those both to this grid to this you you ID value the zero echo 19 The whole value there is that it allows you to use various different systems All you need to do is internally understand what is the member ID you're using and you call us We don't know that it's John or Jane or Sally We just know that you're looking for that particular connection that you are in total control of and we don't have any information in our system That is valuable internally to your system As far as knowing how you have things laid out what your core is like how you use member number That's information. You just don't want to leave the external perimeter of your own organization Hopefully that helps give you an idea of how we use member ID Get you going on the on the path to creating that Identifier if you have any questions, please reach out