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
- 52b25367450bac2ddd1a817c55fe687ef3fbbf73ac1ccfd7dcfc2c7646013ed7
- request
- 50d5830b3d067ceeb98cc3b1256b41b4e6c3416584bef7dbe35762619c7807ee
- transaction
- b5d9a3f706d52dd5788b3eed80c980a0aa07cffd2d881f2f2824b01b87133da7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22735
the chainentry 22735
- sealed to the entry before
- 55502d2a8b252cc8c819b46cd9b10814c9a4131ade459b5ee683bdc314fb8d85
- this leaf
- c51c9beacb3e5c0dbe2f165103b0f66fdb6197060d081abc3938e161ab95c1f0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kIkRDKgGNIHQAKzr76AccND38xLumrOZOZ0Xf+jMDl6U1Zme5vtDogYPXzE0Di+aIADigj5z5ShLFaQ0MyJpCw==