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
- 14512d1ce4b86fa1b709ba6be27326ff2a3cfabcb42ea06ee2c340272e2a9a85
- request
- 328eca4e0d7423b1b596498083dd2288bcc030e261de758ae800725a43704a46
- transaction
- a0f2601ea156306e68d7b04b086a2866db74e08dc5d03fdcedcfc7632d6e5366computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74010
the chainentry 74010
- sealed to the entry before
- 47f826afee65059f6294372ce2f7b525146ba7148d943146b625618a379b3d24
- this leaf
- f1100c73cc12b3fe55fc5ce14f51020992c6741c959d792fd1f1a058799a1eb8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EK/bVJoyfZQyvdxDE542Jiinoyp1CA7LGupwc7Xmm0cBeUNlqpJNcog2avP6EezV08gY3+d7uwXA+dqRv2PPAg==