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
- d4248a4f211dbb64c8827b7466003166d2007f59d83002fa8067f1d7128c0c1d
- request
- 1aa5718109727c42af671edcf7831e50e7111e3116835f900bea5219c0ea62c5
- transaction
- 3a873c39122d1017418ee899b72373ab0c62cb438cf0e7cd160fefcbfad166e3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34065
the chainentry 34065
- sealed to the entry before
- 1eda4af4c5cbb2f9a71be7556a4d4cf6ef9d0be3a76b6820dcf8a3a64c6217d4
- this leaf
- d57f6fa434e85e5c7dcaae4b4671de5a26a81b0e25a3bc922f1f11fc4d976675
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DD2QQHlq5FnLr2Um0X3WvREKeZQwyLETsX0L82sSdGDgNqadHsH69IbhQRv2+t/O99rhI46CtOIC4kWHetVkAA==