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
- e03278bbf4d311948cf0d2d7d31140e224ca93c936d1765f50b4789788763887
- request
- a519905de43187ede5cd17965708070f3cbe16eb58d1a9b2bfda7582f0b4d5ce
- transaction
- 50a47509d76033700119bfcac90bc08523a464d32838ef1f97d04e3e4d8cdd67computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57650
the chainentry 57650
- sealed to the entry before
- 51e2e3644403a250411b8be73bfb7278f459e1255e3cf1e1c1adf9598db510e8
- this leaf
- 2fdab0ded41e8f7ba967b5687bf94366f6fe4e59863ace7ecd06fd5a653b4914
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8JGkAZs5vY1GJ/zUnieZ6nOtZwnfYYyxZMDB/hlj1+z8U/aattRdeMqNRCRAeQNmhrZvrfONinXIQVNF+ugRCQ==