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
- 36f286ad4c19a32c711ddf642f090f64354607656940d357e54b20753922c80f
- request
- 2ee92aa3002d86f481d1f8c6f698ea75419ff4087a2a0a17aade45841040a94c
- transaction
- 18613d113a113af9c57f906bb25e0e373fb3099f496da537856c07edfed0de63computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35329
the chainentry 35329
- sealed to the entry before
- c3250ec552f550d87c6d519f1d88760c74a1d5fb0b007c7cd26a79a1388f598a
- this leaf
- e1cceb2580f258d2162a711d72829089851498a6e006f667adc8c7ee71e7dbfe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6BkHnIl9hRVVqNufpYlxNBHVD/yY2uOCpwOkMJZqJR1SaV+rzVQ22/b57kqe7rZ5V7DAhLMwtV6fmx10hNeyBg==