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
- 8466a4bedb558004356e3621ac85b2c6598877f4d16219f6d7ae547a0000756b
- request
- f04932cd1616edc605e110feb0a4d4f7b8150ceb9de16625e28ab6caf3bf2e3f
- transaction
- 8e44fc04cbfff7ac05c78310c5bc08d4a6b9ead38379395c8c74e48f20767554computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46638
the chainentry 46638
- sealed to the entry before
- 38d2ff9c38431cd494095f75ad251f932597f6ba6553a5b22e8e8f57bbdd5015
- this leaf
- 93e5c7fb4c66cc84aa6f2a8159a40cfc0f6c8c06287c3a98386c13f5c61c5293
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0+KBbicIr0JhjJTressRAV+H6ZJRJCbsRpnFhhkIrAixFpTWaE6EHbgulODglQ+tGWF7N7qhH6XkxGo8ja1yDw==