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
- 6002482b8c1d3692c4fdb47cf73fc016a541caee644f291887231345f0fe6f8b
- request
- 382f8411779aafa8879fc2c030684d257a118e9c13d0fb653765540033a602cc
- transaction
- 6988404574e4c0839541df95fed004631cf478c861043b1a4c326a8dce8ff880computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69802
the chainentry 69802
- sealed to the entry before
- 6c694e358774512e1909489b947f2ba8c8d2e177906bd34fd001f3cdd6df97dc
- this leaf
- 99b2f118a1d677138593e13b0f186e96a2ad1411d255deb24397e9234162eb4b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- niiBAkJfvUgFPCT2aPqZnaEot91YbPur0WG8KisMG9AztohxqyGyvaSHvgi5HD0XaV3fZPUPUKrhoVCU+LI9Dg==