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
- 4b4a03431e45c4e6cde7d469bdb24b9940e613a6294314b0e31287f7f901a342
- request
- 77d09c0cef07050eca10c1870e7551f28e40865c0720d44996713fe6c5b9cd3f
- transaction
- ea1a655be72a106141418f4cd835e10856be212c8029f389ae34f90b8f57c83bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45753
the chainentry 45753
- sealed to the entry before
- b7426d80a75968338a59156a0555158c2d6f76596a361c249eb4ebe46786d92a
- this leaf
- b14440256a8be660d06076355bd4e59d71c2fde133f5a978b631c80ac9e1c71d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +uibK4Eh939AQc1cWyRRcyaHMOfVfLZDROlYClWafd/Mom1ssyKC/Niv7y5EQllBwc4Z/Sb2gnF2MfhVimf+Ag==