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
- 3c0af4f1b09798470c13f7c6a71e3f399bf4395bc2d0f92795c53e665e5b06eb
- request
- 67abaf169e04d5ca3c38f33a81de6e34844fff0c64491ea22f3b731c56b82918
- transaction
- 249d47f90fc2f000f405771506b5c9c595bda3e27827ce45268568507840021ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33388
the chainentry 33388
- sealed to the entry before
- 2f4f2bd603c10f88781c5e483f4bdb0841d978ca96cdc7535107206a53b22e87
- this leaf
- b4269e99eabb90a7f034aaf332bd468c8f0275140f004794e2b1f68d082a0abb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FFTBypHN8RT0LUbQx0U4aM1aw/gf7urPD4yT+NS8MkeZqAsoPjj7dBOcB3/bucaaIfp5659gikmIITpBoFvbAg==