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
- 5bfd224cb82a0b5a39997f3ef07c51ffbf5faf61f9ad6a7376b6f2a2ebce6184
- request
- f83c00be120f03a96bddc4128b36d2eee9b780b891d03e3189965a7af48bbb29
- transaction
- 643283a28c693485d07882d5bb12573dbed8d1497140ad4478981ff4ec6c1e80computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56330
the chainentry 56330
- sealed to the entry before
- db2744811e569a5c11f89f1f07edafd629c3b5485a686ede2a90ca2419d90ec9
- this leaf
- bbfdc89bfe4722462936de2c06265a5bf10ece22cda69eb7fbc01214b408bd3a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3h+YGwhzaqPZPSL0pM4yjwJguu1ppDzp+SBwDeonWAIUXG7+EyIHfyYgye4NR3kUY2qLkXoehIORfR0w5VR6Dg==