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
- 4ceb8fdbc858fa0f4624736206e377b536a006880bbdc591b6ea0219b06e8a1a
- request
- 4e6829f20ec7a6bb5cf835adac5204e0f052b90a5d9066e00bc94f2a714e5b10
- transaction
- 3ceba0d94e3f9552b6e28e062eed7336ba854cc1d7777b411e5bc7cf638dcbd9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30845
the chainentry 30845
- sealed to the entry before
- 576932eb39a762d7182c6acfc5946a146fb18048dffcb1ad79ae52609efc01ce
- this leaf
- 2ddf3d9de15708e17d6b0c2b1d2d3af97a38d0bc254f1658a679cfbc6235c260
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- piKyY1uUy1i8eg1hGwjgN8jeA40MjQYJJufH8gEe6D0socSam0o19ZEmWEV94Llr3NORUXfoLEqTzh97sqjPCw==