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
- 82407a63fc8b643aa78b973820ff5e9650174e611b5c457d63b09e12fd63dfb8
- request
- 69f8a637020610fbcbb69c6d4811c8784133efaa36f200f2fb832b4bba06e33f
- transaction
- 3813c9354a31d024bf32edbbc9af74043ae40c52cc4c92c5663133e3794219ebcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15087
the chainentry 15087
- sealed to the entry before
- d65d5de90421404bf45a9736309ca400480fb0518d5d126cd467c5f873b73435
- this leaf
- 20892359bc5de105ea7aad3ef8893dcc7be7ec28e3d8ed73b001325322fac7ee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UMvRf9MBbFFx3fR6QAzsdOSbMHZElgK16oLSj57eAzPJQP43D40uRz6p++0IZMvFkFxVBnqR3wkT4zkseAGoAg==