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
- 14efe05899d25dd84b8e44b274b63420207a377a5244e778ba6e16006b4373f7
- request
- 7200a00b8b80dcc953acb92469adf11816f0ac650c57defe48f40485b23550f4
- transaction
- ab1b050b0f605c59c03576207d40156c4f8249ec960f37fd1116c9a0f7e3b0b2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22894
the chainentry 22894
- sealed to the entry before
- cd29cf564c988fe7b2b86624ef6ac03576d6d07454f35d10692bb18f95ba37eb
- this leaf
- 464fc2c104cf92080afd7dfc3c87491b170664a1e014a0e4db58bf691b375f60
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lvP2Y5pdby0GsJEtgBKUUe0186oCalSZJDCKd9J4qOw4E05dxrM5VMiPYF0T/UEt9FYdLWF7kIlzyInR1R13Dw==