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
- 86b070305f743ee2c34ff179de5de2c3179d58a203d243fd95efff4001b45335
- request
- a74035f8381c8e5668771df782cd29bb5ee9e78d5622d0573d1aa950a5a35d43
- transaction
- b92883bb0e55c2a12195bf281ce0d1b5ac19efd44c78a9fa7b5c3ee4d811b598computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36144
the chainentry 36144
- sealed to the entry before
- 146412712d0fb95cff45b93ff87ac7d6aad85b3b6a57d7f6904be7e85d8a978a
- this leaf
- 92a8c9c8af93b69d1ce0bdc24ac28655ed9289e90d437900a61ff5dacb402697
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vWDqIvS3hvY78FTevH7fqzR8RjCeBCGXsUKvP8YfixXyoDwJvPoUlYq/CemoHIbaB1eE3Yphm23CCERCC43xAA==