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
- c5ac5e873c68db9504379fd6426defe1edfde8907de989c963ed7160205bd997
- request
- 3700cadde545502d636ea3f117e24c2deca2e793d0a6825a1b09fafcf42fd42c
- transaction
- 75eb76714fde7983bf6410645b5e265537944bd7400f5a85fdea5275d9f71bbccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8521
the chainentry 8521
- sealed to the entry before
- 3f0d3cc124742efb4c879adbf3a900b4a9325353f93545e8a98f92f72b295f4e
- this leaf
- 8bd1024371091aa0e053065616ff254995e975c449a89c1b553b1f040277cf17
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RGJRE1/WEy1Y67cidaGlUCUsIFRYkyDfeorB/7zuDn6OGKSj51d6/7Om3zKk8UdtVawGRkqhR0F44fvNK9a5BA==