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
- ef596c765cc1ae05a5ecc6b56fc43b191d1bda43f6799e3f916db84b54faabb1
- request
- 684763ed90c9370b54a51c8abe792e10aca7bc1a91b6067615b3270073be7696
- transaction
- 2861e1a4ae43466a04436d1d2c304653a9fa4eba26039ca5f801bca5d57d6843computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52304
the chainentry 52304
- sealed to the entry before
- 8724c10262ae8e8981549b84457eb39dffa363b39b1cdff58b87714b83401332
- this leaf
- df8a34b0273f61bf082367372cce4fdd4a5af58a9333b603b5ba96e5f477a02a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- O7YSo1TtqwAPpa6XZku6Yl+DQ8MMOD82nMMvqjjOSnf06HeOh9wsJDDl+/gAk5rh1CPCH8mdRpQN5JYvry1XAA==