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
- a073b7512e97628733a10bacf99a05f69e9f2f1cdc4ad82a3862f0bcf9a69b54
- request
- d176694229865c6992c53575b508efaf121441c6d749848e49b5c3fe1abace17
- transaction
- f30ed73641d5be934839e620655a992fd598af6ce19933b701791101782a01afcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74493
the chainentry 74493
- sealed to the entry before
- 82d7b4de732265ac582eb0ed3da6e1021bcce9c47e84fc2d2343c2bbedb5eeca
- this leaf
- d4ec8d06f3a23abf12c8ab321167e57b6b5d540a2dc76d245cbd75e5ce4f71ea
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bo+74sOJQ+rvii4JYMRpf+EYZXQwdeXDNaCGjAvRQS0fudHVbyuXdHYCdETUhbNqizFbKmkSCf/8sXJyNPAhBA==