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
- a16a35719def44f0d48620041e9adaad9cf65ace74c39e34409e3222b273af3d
- request
- f5a0f5e85d302e2b9ae312b1b1c01945ae957ca957a82188fe64300479819d89
- transaction
- cba7c43a85915a217ade34d16a84b4babeb90433bd919b21e350af759ae55789computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33145
the chainentry 33145
- sealed to the entry before
- 08a23caa9dc2d74a79c7a068123d5afbeb526b86f51b2d9df6a2e2dba6bff87b
- this leaf
- f9c95df8a43b3d99f71e6772dcb6ef3ca45bb7ef1a5b9f49510993a85b5978ca
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jOOdNuSaNIf0KXWpq9AgzVuuL4eksCu6aMUc5pqDKQ7XhXjPRhZj7qjkuTeSzHH9DqWeuduVnKiTs5SccokLBg==