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
- 2c6028f77618de4ab046d6c0607269c8a08f0232c4f015125b7b9cdcdffcf429
- request
- 4a10f24ee118eb7cd8f703bc085d5d2e8ad01a1e94bf74943adf38bac0fd6556
- transaction
- 94b490d512caed911f315131916fcc49d3c58fb38829024e1ab8ac7b69cafebacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 77702
the chainentry 77702
- sealed to the entry before
- c0027220854d2429b97e4e9a0bf81ce8a85441a6a607918afa9f5d1f01aa72e3
- this leaf
- caf8e9132c1bb5b20d2d7ca4e685294c9db7de67501bf56ae8264975b7948c27
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bS9Lgu+38orVd8RlMgW3aR5JxdlpPwzIsBHLDvpH/7Qo3iEKvuTV/9MITuNkupqXRVKEgBMekg2V0+/qKYDGBg==