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
- 3ca7c7eee101e58c478842640953180c42d751229e04d014da25603a19621870
- request
- 7274ad166fc3d9b5507d8fd701f533d197ff20b1f495df54ba0b7b147cf60069
- transaction
- 205b2bd5e10d1ac8e8f07255c3c328392a847e0be31726b5d72a12b80ecf87dacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52737
the chainentry 52737
- sealed to the entry before
- 196283c9b7e3d6c8d1a200c0772b5e88894bbc94c5c69e083c28b495cd96edfc
- this leaf
- be48eb3edd1f4a303bedf5eea1328e96268537f55b780694bccfb0eb72563ee9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xWji7jt3AFXCp+tINPW30xCZO5XHvftXwIAaNjjS96nFfwSOqKm/oEcJDJPQDR6POQ2IB2ELAEN+9/uD/VE3AA==