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
- bb5dcd2b4700cf070fcf9269a86365abfe2ed258a89e1770b5a773f3e21fd30b
- request
- 50a400996c2eedb15c1693378199f63a9c79b31a2152ebb15809dcb1ade1773b
- transaction
- 539f654fcd0d19c6cc23e0a59202169a07d76b7ffde7a12f35a81ee30b6e4019computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31749
the chainentry 31749
- sealed to the entry before
- 08cd0075e6311b5b697ace0b5e0d5bad46970d45c87b719d543b70f280a9dd29
- this leaf
- 9394a12eb211eaaff5becb2940069c1a22397c79b99f26e6aeae82f2909baab3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vB2UQ9Ds5rzGmQvX0j7AuBathAYarVl/F5rUpRHimjPSbR3Zii81h7X/vTqQEV15X8YQR0EL5XOXyf0no2jrAQ==