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
- 963bb9ebf3a1c70f749c8d6f7cf18f5e121cc14a3c4250ef06396cea2f50be80
- request
- a1920131eead7aed7a4a969506172a5b1ab773f9a3e4525272aa88ae940531a4
- transaction
- 238e882ed7c7033a35e609d6111fd144770744fd86b5da355cd82e633f8e4ec7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55126
the chainentry 55126
- sealed to the entry before
- 46d43a019d830a09bae32a862c439293621449cb69fe0d8e866ff6cf104a27d5
- this leaf
- a7febe33c592293889d646bca2dc4a034423626ea8201a44a0439bc27d854398
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MtqBdHjAzUyPCwKhv7FCNRda6f+jjW+XsTiCb05UCj2ViQfxyMbyFXHsGne33EdnTJTG+jEsV7ge/o2LspiNDQ==