HumDay

Screen order for payment fraud in Fraudlabspro FraudLabs Pro Fraud Detection

A documented Fraudlabspro FraudLabs Pro Fraud Detection operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.

Automate this

What this operation does

Screen order for payment fraud.

  • POSTChanges dataapi.fraudlabspro.com/v1/order/screen

How HumDay uses it

  1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
  2. The contract names it. Before anything is built, you see exactly which Fraudlabspro FraudLabs Pro Fraud Detection operations the program may use, and this is one of them.
  3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Fraudlabspro FraudLabs Pro Fraud Detection operations

All 2 Fraudlabspro FraudLabs Pro Fraud Detection operations

Questions

Can HumDay screen order for payment fraud in Fraudlabspro FraudLabs Pro Fraud Detection?
Yes. This operation is published in Fraudlabspro FraudLabs Pro Fraud Detection's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
Will this change my Fraudlabspro FraudLabs Pro Fraud Detection data?
Yes — this is a POST operation, so it changes something in Fraudlabspro FraudLabs Pro Fraud Detection. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
Do I need to write code?
No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Fraudlabspro FraudLabs Pro Fraud Detection account.

Where this came from

Read from a published API description for Fraudlabspro FraudLabs Pro Fraud Detection at app.swaggerhub.com/apiproxy/schema/file/fraudlabspro/fraudlabspro-fraud-detection/1.1/swag. The description above is the provider’s own wording, not ours. Last published 2019-02-26.