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
- c01633f3ed40dc043366d96d384a83475d328f933d1743b89730deeac6fda24e
- request
- f219a306575aae05fd6c50d19492873510369dc3ab965f84b412c68bde4a6600
- transaction
- 9ad255b70b8b049c03b26a246cb30e6a5f7ed718b3376d4429f69e79c359abbbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1167
the chainentry 1167
- sealed to the entry before
- 8e5f9e9cf7920d03c19e53cbcd0aa094c30dc0f8574ae8b4d0c8cf93aff950b2
- this leaf
- da44915c70c165095971aa1e9136e229c42d0ecca47c7ae6083c9bff7037bb7a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Y5n5sjD/LsAGedHuu2CwhiHF07D7eXZOTwQy0CqJdfHWisEnc2590RC2658vdgopSdsKqy3E7je67kOWpnBYBg==