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
- aa43a1e01926cb629a9fc27b15676459c9c77c693f9f00ead610cd0244be835e
- request
- 90db8ffb63cc34b3f5a552c9f758cf1d662ae484c8b46ca4f475b201af78592f
- transaction
- 41306e355812ac8c67969ff4ba93945434639493eb000599afba166c3040433ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46367
the chainentry 46367
- sealed to the entry before
- d1f888e3d6ad73a1c6c112a36350913e64daaa17f5ee76ce4255a7cdee5ef005
- this leaf
- fd06bd3b406dc32420a7adfdb1f287368d70481698d652df6c7d2de610cb9841
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XuONv/mRs4Vol7c6eHlavoyPg5Nz4W2LcO3VnKT9R10Kf5sYSOm1cWPUsg5FhCkSq9pzp3lJXHm61sFd5K4fBg==