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
- 1fd25261c9470221a9b95a9204e0ae642df00de08b3a85ef3d48b0e76f45ca53
- request
- 0d566bf40a4e730120cf3e4a552a405640862d880a6222b9e99ca9fa72f3ad1e
- transaction
- 6242f17441e6ff59545c07e6759046d7e72b570a9458cd2e7fcc976e6ba78970computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15675
the chainentry 15675
- sealed to the entry before
- fa21b46ba594b2c7a07564d6523f2ecaa2069c22613390fa582b195f4034a764
- this leaf
- 1197260def98d101b94a6889e96e7373bfa9fada9cbbd0c1696e45e9e40a02fb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GB+eHKffjNQfDEhdEgmj2yFWoxY1KmCo3kr47tmC1gg5CD8qrD/VzLOaJYC5sYb5Bvk3e6tmrKRNSM9L7srwCg==