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
- 78f164e952cdf6ad023161af3121c5c9b638ceabde3f042171c7d2edda9e5fd0
- request
- 7170dc2760fe87d74bc9bafceea89be35600209076e6abf5c8153645be794f18
- transaction
- 8fb2e82c03dc612ea625d74087b4edf975db68335f5c4608de039c84204706e5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49684
the chainentry 49684
- sealed to the entry before
- d9d1c6e8169079ef5daf1f0e7f0d2d8d4e4a6f281dfddd8cc234f0507b0a7cd8
- this leaf
- 7d3e95f87adfbf82fa455ae490701cf6d5902c0e6a33b64a5f5fcc69f6c6af65
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bG4k3a/WpUGVpOuwJC/0zkNo8cPvnLUrzD4eZI5iAR5I81wtEoA1BvjLVChCOZKYRsA0AsAMNyv0DGt+9KlEDQ==