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
- 162df649cfe104371a2c04ef28e87a3c6b17e617da9949a1edf0405ef9765e0a
- request
- b7032ee008d8084a010bebe32882ea368825d99bc6bbd255c8a668567e239005
- transaction
- be6edaef87c254e245958421f18800e90e175e046a75ab28e832dc7f7f42e158computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50987
the chainentry 50987
- sealed to the entry before
- 9bf24e6728438d04f7653529263f24617498a96894e32f748801e71128d2b528
- this leaf
- 96682c8ce1758554b68b3ea89a6fab64120759cd11a1cef76bfc1c11970991a1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- a9GUdDWvGiLIGk2Gq4Ifva66hVO09ktSX82C67pakMpoeknptd5tokxMIPlCy+BBDHUbQiZHTqDGJHvqC3NhAw==