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
- d66ebd64ebb04bad0b17f02a5c03bae45d997c4283241a5c1dbb993442f082fc
- request
- 7b0ca00a386e59590e44551d56dc1135999dcfd72b463116aa08941334cbc964
- transaction
- f1f81132a1a9c3b3687272d4426274438a12fd3f9de3c5181e97ad3962749165computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51206
the chainentry 51206
- sealed to the entry before
- a6cd8baf32d729f6bda517e1d28bc64f1ea63c2ed31e13e6166feab40d60d7db
- this leaf
- b24949902c17be7673e1e75ba4c8a409b89149e089c19dd529f35a8d043ac957
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- W1WMeonfhx1uwO7Omc9hYG28dpypfz8F4sZzkRhkHzx1hj3zOF1cZPWrLbTu5kvYehiYUqe79ZZBH40Tq2qYAg==