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
- b5e36c57937fd701654d5cce4afedb4eeb5384cda2fd76765f63c31d9d4808a4
- request
- 46e64448dbcb0f9be06d03ec43f093fff1dff01cd148249dbe2f73ebbea7b827
- transaction
- 128fc833168497b78c5646801ab5a6baf21d55b7948684947219d0d051306ff3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62518
the chainentry 62518
- sealed to the entry before
- 4ff4bd80d4ada23809261dfebb0cf9bfcec6b8d74c4cd3e985ea209e9ec29226
- this leaf
- 6bf76452adcf0e5e99a1833798ceca4d89320f724ee28fe5a88dcc39b45185db
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- n3tH/lRPVvlAO2Tw4zXTk+ykKqPeMBFLSMx5bfj/rh869PrFqqWaPNvxA+vHwTxvs+3oE8mmFWoqdtIHWT8FCw==