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
- 6087cb17e534c73c11912e1dc29ceb3445dc48c22514416b3b0cfaee7bd86611
- request
- 44691111226a5fc033aba71329062d299364a06de56bdf3c69f936183f212dbd
- transaction
- 1e63776ca38270fb9abc2bbe5d156fba21bbfcb1c924621b8d32ddb17b976609computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24202
the chainentry 24202
- sealed to the entry before
- 8eaae15a95ba98ab1fff4a72d630c99c27617960bdd89e0d604eb617ad81239d
- this leaf
- 5aa00ce7a9eb5be52d5b3e1ee7fb39b9a2aa803883047605b8f22e18557839c2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LPmy7K9fGp+VeV2ECqG0pbWFHgqTm7fD+xznQ22WkGA+csPF2/nNJJd0bO9tnuvzU92pIrykeqMI9sy95V9ICw==