Tokenization

Tokenization - for passing tokens across multiple parties on internet or a network. Common examples are passing tokens in credit card or user Personal Account Information.

 The idea of tokenization is to send a token to a remote party instead of actual credentials. Once credentials have been accepted by a verifying party, from there on tokens are sent between remote parties. Token is a random but unique identifier for a particular session between various parties. A new token is used for another session so that it cannot be replayed back.

 The key advantage here is that the transactions to the remote party uses this token instead of revealing the actual Account No of a user (Privacy). This not only protects the user's identity but also minimizes the risk of transmitting a user credential over unsecure channel or eavesdropping (Security). 

Example Use Case: Pay via Tokenization without giving your personal card/credit card number to the merchant.
Token transferred from Device to Merchant payment Terminal via NFC (Near Field Communication)














Cell phone/Device ------- Terminal ------- Acquirer --------- Bank
Bank issues the token to the Acquirer, which in turn transfers to the Merchant Terminal. Bank maintains the secure vault which contains the users' PAN or Personal Account Number. Bank generates a secure token for the user's transaction and his Personal Account.
Advantage: Each transaction that the user does, a new token is being exchanged with the third party Merchant who is never revealed user's Personal Account Number.
PAN: Personal Account Number
NFC: Near Field Communication
Token: a unique identifier (a string of characters) for a particular session



Comments

  1. Daniel murphyApril 6, 2022 at 3:49 AM

    Loved the content all you shared, I got what you intend; thankyou you for putting up; I also remember one such article aboutAre You Looking For Most Popular Real Estate NFT Tokenization Development Company. It's Really awesome!

    ReplyDelete
  2. UfundAugust 18, 2022 at 1:16 AM

    Amazing content! Thank you so much for sharing this great post with us.

    UFUND

    ReplyDelete
  3. coindeveloperindiaNovember 21, 2022 at 2:45 AM

    This comment has been removed by the author.

    ReplyDelete
  4. coindeveloperindiaFebruary 6, 2023 at 2:39 AM

    Very Nice Blog!! I love the way you explain tokenization. Waiting for your next blog. If you are looking for real estate tokenization then this blog is very nice

    ReplyDelete

Post a Comment

Popular posts from this blog

VMware fix for Invalid manifest and ova file import failed errors

Image
Recently we got a OVA file for a virtual machine. The vendor instructions were to import the ova file in vmware Workstation, Player for Windows/Linux, Fusion for Mac, and VirtualBox as well.  The instructions were to take the available package and launch the VM with VMware workstation. The package contained  Module.mf, Module.ovf and Module-disk.vmdk and a Module.ova file. The .mf and .ovf file were 2 KB each whereas the vmdk was several gigs. The package also contained a Module.ova file which was several gigs as well. OVF           Open Virtualization Format MF             Manifest file VMDK       Virtual Machine Disk OVA           Open Virtualization Appliance The ovf file is a xml file that contains metadata for the ovf package The mf file contains the SHA1 hash codes of all files in the package The vmdk file is the disk image of the virtual machine,  VMware Workstation or VirtualBox. (vmdk format was originally developed by VMware and is an open format now). All of
Read more

SOAPUI - import certificate

Image
Note: SoapUI has two versions, one is open source and second Professional version. The open source can be download here . (confirmed link 12/19/2018). SSL Handshake issue:   There is an Issue in SoapUI version 5.3.0 (and 5.2.0 version) with SSL handshake error. It was resolved by updating below in vmoptions file ( refer here ). However, the error that shows up while trying to load wsdl is "Error loading WSDL" as below The fix is to Enable TLS 1.2 protocol for SOAP/REST calls in SoapUI, by ammending the vmoptions file to add the directive for TLS as (-Dsoapui.https.protocols=TLSv1.2). Refer here . Update: Version 5.5.0 does not have this issue. If you are on 5.3.0 better upgrade to 5.5.0 which is available now (Feb 2019). I had above issue as well as another issue reaching to https endpoint. Upgrade to 5.5.0 resolved issue. Select "Check for updates" under the Help menu and you will get option for upgrade. Select upgrade current version and accept all defaul
Read more

Centrally Managed Users (CMU) - New Feature in Oracle Database 18c

Image
Centrally Managed Users (CMU) Centrally Managed Users or CMU is a new feature introduced since Oracle DB 18c which allows simplified database user management through integration with Microsoft Active Directory (AD). Beginning with Oracle Database release 18c, version 18.1 and later supports direct integration with Microsoft Active Directory (AD) using the new centrally managed users capability. CMU allows the Oracle database to perform user authentication and authorization directly against AD. Benefits of CMU With centrally managed users, users accessing the database can be centrally managed to improve an organization's security posture. An enterprise user (a user in Microsoft Active Directory) can be exclusively mapped to a database account, or many enterprise users (in an Microsoft Active Directory group) can be mapped to a shared account in the database. Microsoft Active Directory groups can also be mapped to a database global role, which provides users with additional privilege
Read more