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
- 00ecb7cb9dd3dab8ff19327d135de7493ff76d4ab12785f2afd70dc1463ce85a
- request
- ae0bb7a63e91fcc29bd22d6c8e1a0c98ce6f24f6a4f6b99cbf25ad0757151bea
- transaction
- ca0702ef1d538f31e16cd55df4d8d934a9152e11b877422d6cb0c1f43b1c2497computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 441
the chainentry 441
- sealed to the entry before
- ef18b7cb2f178bbf1a63ed53bdfb1867429a553456349e151e62ae887f004157
- this leaf
- cf8e6bfc11e73a66b07cdb4180598762b8eab53e88bb00850948ac89fdac8f0a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Xht5+c66Z30r7XqHeBP/hifcP4CKzm6BMYIpeSARzBd7h5bzynPHOOr/PFr1/EKBKL1H1G6Ou5zo9p7Cfg6zAQ==