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
- 3c7fe1df710c08786b92130b7021000f2e5d130813fff9c659ab31abc1b20212
- request
- 1554b8e1690ff8a85581065098ea8f5b03a63b1080add419c360bbc311cb5089
- transaction
- 57e2bb1b66300d8b219e2646da46dd49d82daf758027b99936f45d70d360f001computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73845
the chainentry 73845
- sealed to the entry before
- 0d9c4e313cc6a37be3eaa43c36e2e257c1d147fb61c8d9f3924eb00d683fff52
- this leaf
- 6cb6421286bd8f24772592c773012bbaefb016d4efb9692ff2ab9e721a5123f4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TelPDl9ZJq0p00NZRrzwdIhueRdyFGAVRzLSn4W1bBQsOV+74h3izGFoYg6s5YgCjtTRe5iV6Ah4WmTm9oB9CA==