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
- e6fd0d9439ff34f32a94b3cbfcaf35fe62dcbd5370605565b07b00ec836d8f53
- request
- 54b0bae51c9118b1250d21f053977c744a7aa6523070f4ab566da190ac319e1e
- transaction
- d38488bf233e6b740c66b0f2212ded4415fe719d45f85bc1f0d4342c79d03742computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 27485
the chainentry 27485
- sealed to the entry before
- 663902429f52846b819db587997e22b74778897ea734af85a6e8bf16a4b7cf5b
- this leaf
- c00d4d387cc6eb2d8c8df8b8fb042011ec36abb751820c425e37d85cde2bef88
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PPY7hn9GqcTT1KBthIIDAmYil0e7OtZLAq6eSe4k2URJBl9xXcx4ydg6uoyn9EElDTcYJygXlI4dO7O87vTBAA==