Hot Deal

How to delete card token issued to a merchant

336°
Deal Cadet
navkr

With Card Tokenization coming into the picture I got a question?

How to delete the card token issued to a particular merchant.

Suppose I given consent to Amazon to acquire Card Token from Visa/Master Card/Rupay for future payments during current Transaction. Now Amazon wouldn’t require the Card Details (not even OTP for payments upto 5000).
Now I want to delete this Token so that Amazon would require Card Detail again and I would have flexibility to choose Card Tokenization.

As per the news
"A customer can choose whether or not to let his or her card tokenised. Besides, the card issuer should also give the cardholder the facility to view the list of merchants for whom he or she has opted for CoF transactions, and to de-register any such token.”

Any one having any idea on this.
News link: https://www.google.com/amp/s/indianexpress.com/...
Thanks in advance

29 Comments  |  
12 Dimers
  • Sort By
Deal Cadet Deal Cadet
Link Copied
teragoel wrote:

Disable OTP for less than 5K with bank

Please read the scenario 1st

Deal Lieutenant Deal Lieutenant
Link Copied
Expand
abhishek012 wrote:

OP didn’t mentioned RuPay card in his post.

Next time dnt tag me on off topic discussion. smile stuck_out_tongue

Then what’s this blush grimacing

From 1st Jan 2022, Your Amazon/flipkart etc discount offers will not work, if you dnt create a Tokenization for your card transaction

Please Visit
https://ddime.i...zZ

Deal's Advocate Deal's Advocate
Link Copied

everyone wants to know this question’s answer sooner or later.
HA+ for highlight.

Pro Blogger Pro Blogger
Link Copied
Expand
MrKool_JJ wrote:

Abhishek (the expert) only shall have an ans to this smile

Now OP added “RuPay” on his post. smile @tappukepapa

Tokenization payments also work like any saved card transaction.

Customer need to enter OTP/PIN on payment page and complete their transaction (Tokenized transactions will be received from the acquiring banks and will be de-tokenized before they are forwarded to the issuing bank).

but some merchants also give you “Single Factor of Authentication” option for payment upto Rs5000 (it will be optional).

If anyone want “Single Factor of Authentication” service then use it.

Flipkart, Phonepe, Paytm, Cred etc already offered “1-click Visa Checkout” service and you will also get this service via Tokenization mode.

RuPay is also working on “Single Factor of Authentication” services -

Upcoming value added services (VAS) from RuPay card (already 3 banks live) -

Now in case of Recurring Payment/Standing Instruction, the subscriber can cancel the subscription plan at anytime (RuPay user also get this subscription cancel option through bank or i think NPCI will launch some app or website. So, you can cancel your RuPay Card Recurring Payment anytime. Just like you can cancel your UPI AutoPay payment from your UPI app).

Deal Lieutenant Deal Lieutenant
Link Copied
kartikxxx wrote:

everyone wants to know this question’s answer sooner or later.
HA+ for highlight.

VD – Vote down
VU – Vote up
Kg+ – karma given
What’s HA+ ? blush

Community Angel Community Angel
Link Copied
Expand
tappukepapa wrote:

Why, there’s is already VU blush

Aree jawan log, can relate to garmi more, isliye,
T : Always remember, food tastes best when it’s served hot.

Deal's Advocate Deal's Advocate
Link Copied
Expand
tappukepapa wrote:

VD – Vote down
VU – Vote up
Kg+ – karma given
What’s HA+ ? blush

Hotness added, vu vd is old dd, after update is ha+ ha- smile

Deal's Advocate Deal's Advocate
Link Copied
Expand
Siddhartha07 wrote:

Aree jawan log, can relate to garmi more, isliye,
T : Always remember, food tastes best when it’s served hot.

Bhook laga di paaji laughing

Deal Subedar Deal Subedar
Link Copied

Tokens strongly depend on the “device”, hence any changes done to the device will invalidate the token. DBS and PayZapp also uses the similar tokenization system for any server side calls. A simple hardware/mock change to the device, like sim change, resetting guid/buid, etc, will require a new tokenization and hence the older token won’t get validated by the gateway/bank wrt the merchant.

Deal Cadet Deal Cadet
Link Copied
BlueFlash wrote:

Tokens strongly depend on the “device”, hence any changes done to the device will invalidate the token. DBS and PayZapp also uses the similar tokenization system for any server side calls. A simple hardware/mock change to the device, like sim change, resetting guid/buid, etc, will require a new tokenization and hence the older token won’t get validated by the gateway/bank wrt the merchant.

I don’t think so. Let’s say you are accessing the merchant site from web browser. Then?

Deal Cadet Deal Cadet
Link Copied

I think it would be on account basis. E.g I have used PayPal on Swiggy. It requires one time authentication until you remove the merchant from list of Authenticated merchans from PayPal

Deal Lieutenant Deal Lieutenant
Link Copied
BlueFlash wrote:

Tokens strongly depend on the “device”, hence any changes done to the device will invalidate the token. DBS and PayZapp also uses the similar tokenization system for any server side calls. A simple hardware/mock change to the device, like sim change, resetting guid/buid, etc, will require a new tokenization and hence the older token won’t get validated by the gateway/bank wrt the merchant.

Porting of mobile number also invalidate tokens?

Deal Subedar Deal Subedar
Link Copied
Expand
navkr wrote:

I don’t think so. Let’s say you are accessing the merchant site from web browser. Then?

+ @Bk100
A quote from RBI site (https://m.rbi.org.in/Scripts/FAQView.aspx?...29):

The token requestor will forward the request to the card network which, with the consent of the card issuer, will issue a token corresponding to the combination of the card, the token requestor, and the device.

It clearly says the tokenization is dependent of the devices; Now from my experience with DBS and PayZapp, I know a miniature change in the device even if it’s a slight sim swap (say sim1 to sim2 and back forth), it will ask a new token to be setup; and for laptops also it needs a separate token; which again gets reset if you make any changes to browser (in this case) like any font changes, or cache changes, basically anything that changes the “browser-fingerprinting” logic.
Again this is all from what I understood technically, I might be wrong too.

Deal Lieutenant Deal Lieutenant
Link Copied
Expand
BlueFlash wrote:

+ @Bk100
A quote from RBI site (https://m.rbi.org.in/Scripts/FAQView.aspx?...29):

The token requestor will forward the request to the card network which, with the consent of the card issuer, will issue a token corresponding to the combination of the card, the token requestor, and the device.

It clearly says the tokenization is dependent of the devices; Now from my experience with DBS and PayZapp, I know a miniature change in the device even if it’s a slight sim swap (say sim1 to sim2 and back forth), it will ask a new token to be setup; and for laptops also it needs a separate token; which again gets reset if you make any changes to browser (in this case) like any font changes, or cache changes, basically anything that changes the “browser-fingerprinting” logic.
Again this is all from what I understood technically, I might be wrong too.

Payzapp creates problems if we port and dose not recognize new network easily.

Missing