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
- 3ad4d5211cd00885eeedda4f5326dddd364cff14aaeb32312e1d4db15611b14e
- request
- fa55872d47ae3c2a907a7c4a96caaa7a526a80438ecd58dfe72ada41c2b7635b
- transaction
- 6df3079eeb01a66a06d5a68c8ab1f9ec7f4740a21e9b5dd5b402f6452bd005b8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70284
the chainentry 70284
- sealed to the entry before
- 1da4278efc2b32165877c54afb4283395878feb763e80ec06a82b4a9689cb3bf
- this leaf
- acd9aea06dc9173447c1f16b50f5894f0b6b91e45435f1d00fd9b9d92228a700
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BKNrhGYi3b7vPJIuiAu1ki9lH6vrBKfpNfH6yyKL6SncKpXDr0HeRUjWMMwOs3ujzHSbW4ojnQdVCQUeactSDw==