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
- 79263926b015b2bf3b22e16638f97067338f62681091150b7e2aecc9cf855b57
- request
- c771cf9efddd81b371521573cb8bba6e0a9f313ce6ff46ae3d0a9bd8755f4820
- transaction
- 0a70dbd00e7f59764402263312bab60098904251c6069a2d361ccd4b3091e054computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6060
the chainentry 6060
- sealed to the entry before
- 104cff9869d7dcd23b9ab05e55d8e9992490fc25c23a29b783b3a391bc7e4617
- this leaf
- fbd702ece62c62450f8fc13e273664c5114ee6349fefe49aa4fa20e2d64b5585
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- zJSLJTntDEm4rVQs5Syqv1uz/fbZMqcG2RL5MyV+BuLNhNfHHNDMB1htAXpm366+9k1tBAUjl2NuhKTJvCa7Dg==