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
- 080ea51d86e3fa754569f5f234fa7ed4cb41f1c2015140f5d3d0eb982c374fc2
- request
- 4a4e787b1f169dce484beeab16d2942d6f0c34b47edfe6fc7c62a0dad6c1c03b
- transaction
- fbc5d9c4826dc1e3fb8d85e3b4cf2de8f856c9906ecdd0e4fe81d557b76ba849computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2300
the chainentry 2300
- sealed to the entry before
- db6a426faf4828740150045be8d327cd6a3b47a281f4ed244ebf765fbca4d727
- this leaf
- 2bac98188d78399216698296aa78321225c3f67853201fffeac615456660256e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SdRPXis/K3gBD4hixjnfjcQqRqgld/3hISomRqmpi7Yz9nl7r8XWRF7whte6907nndRyVrceS+/K3h/ErlsRCg==