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
- ff49a7e955e543feecfd447525a0e59e774a522a139cea822553f9001231008b
- request
- e0148282271983ba11e1e1e5ef879bceaa9beaad75173e957c06bac55cf3c7b4
- transaction
- 0cbc0c597831840a646e169d29e24d412048b38c508778174716719db238bab3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11298
the chainentry 11298
- sealed to the entry before
- c9810ed0d523fd7488bdb26377fd7dbfa8751b89b9deb58376f376ce05fa1a47
- this leaf
- ac0761f78c292e12d219d5ea3f28aa3329cfe18ab8f9f143b9246e29a25993ee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eBDF4osDeblYi+kybXU8WE/E2qnFHcZ486S6LawYPx76ZnVy4GXW9e79auoouqpzh5c/QMe44A5ttNCDwpZ1BQ==