why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 3f83fa6cc924edaf679868c74e9ad1cb1a730adb789ccb6b750ed414a7ebdb1d
- request
- b6637b879e3e29e3899e8d9e843997a34fa2797d17536a6657d24a2c6958b92b
- transaction
- 24e7a512ddaac17a9131575dcfadbcd79b06f1e9ceb345c14579ae5b6616b242computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62503
the chainentry 62503
- sealed to the entry before
- acd80cb6fe903db9d3513b65d1312747e9a469f7de160661070dcb52b38f8d7d
- this leaf
- 111691062feaac6e838248c13cbe95d9238e9202d873133ada2edc89e3d6230d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PP1Os1tuxTOngj5V4uql5kAAxayr5f2Ur44fbkByYfwRxxXKJsAFaph8TV6fT9HZmQ3FYY1U/uD3mgv4hRTxBA==