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
- 0882fb951560c3f2c82a9ed0b9bb7e646fc621e40bc611b16edcccf1e63af018
- request
- 959ac2d60452116f5491b047ea795ed45efb689258cbb6290965ec03d8ce8ed2
- transaction
- 023eae5bc881a34cca7118d69bc865f82328d30932ebf8f64379666f4e551eeacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57945
the chainentry 57945
- sealed to the entry before
- 486d84df373332ba74960d60a24d3f00c56e9314e505fd18d7ea9d1ffb7b3497
- this leaf
- 1f923a77b6eba7bad947fd92f16d5467181dc5bc0a79ef4ac7ac5cbda013b51e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fvcPCwH+aRyDjg9TXQh4Cj3VZquwFDB7NFdxPBuXs0aBD0Ncm1H8nw+WAIj1iIGzHEJa9Bymydr8sqTG8fpKAg==