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
- 71059ace9a6eee615a60a0da7999e5e41f696ccf3e44968ccdba535d38af1b41
- request
- 4cb898a33e5f09542bf2d6658b4841473a16ded070784c2d6fb46b4432e491bc
- transaction
- ac85c231c4c6033d15b30a0d12df543be51983cbf138bf7366a9f129fff0488acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27496
the chainentry 27496
- sealed to the entry before
- ce8e6d1bb0d4bc5b0e0fa0243d9a2d691f1c6747b6a40af7fc0ced44f4076294
- this leaf
- 42c2d9aa12f841b44cb8343241d81e5cb5c168391ae87a933af5bb008d7e5de5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KszRmpyPaJ0ThFsM3BJAke6WtpZOeVr91DZoKTD9EStPzrGAiioqd0AcOX4emMQPcQE911fBVBuMseDRb/YhCw==