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
- 338a529d6beaf382b2c557038033a0babedd299fedf3892a7f05c2129fa3691c
- request
- 17e303719fa93d0486c3fa3971cb7153b2a6721bc51820f40f56233f76d1df11
- transaction
- ff18a10bc5f6eb20792ea95e84a85e352a37bb9a7bb14779602223d6875aa282computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23477
the chainentry 23477
- sealed to the entry before
- 146076bca472244d3f4fa193f1cfe1a0f6e7c6b79a98cfc22c0165f44cf88ad5
- this leaf
- c950f6244101b54d94316e7ecad7c123470f5e55473fa6631af7f43ba0abd122
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6wF3bMg9bMweTUM42beVBeIgMRsSPyIHp09mdyrenGOX9xBGKdEls1X150aEGQNeYdtKoXuAxgLmBX/0TcIRDg==