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
- ad0db4264a6b2965f0e2e27910876f86f9063bcef27e61373a2d2d970ee16dbb
- request
- 201e7bb35aa37212d1b6efea0161a7dadacaff595ba8bd23334763fda7e53cb4
- transaction
- ed1dc9120a3edb5830be93574759481018b5ae237970cd120726bfc6a89a8ab4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76188
the chainentry 76188
- sealed to the entry before
- 6f5cb77c6a7002415383ed592df1606bebea1ed01024f423f9c9b87fa4d3c402
- this leaf
- 811da837ce93db95407553af5d74dd1242f0f384a93a786c791310f1a5ef2fbb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xHvn0wyIj4gewNXXncfiWO55MUQShx7A6UZ+IYbUOHjt0i6vUAh1G7kQoQlUBE561sz/EbNEszpwX0xRDRZBBQ==