NewebPay
Neweb Technologies
System integration
Lets the Agent look up whether a NewebPay order was paid, read-only, using the store's keys held on the platform.
Connection routes
About the routes →FDE Rune
API key or tokenWhile the deployment is being designed, the FDE Agent looks up a few real orders on the FDE's own computer to see the store's order numbers and payment methods. Needs a few order numbers and amounts that exist.
Workspace Connector
API key or tokenThe Agent looks up orders with the store's keys, so every end user (e.g. a member of the organization) gets the same answer. The keys stay on the platform, and end users and the Agent do not see them.
Documentation
Lets Asgard Agents answer "was this order paid?" from NewebPay, one order at a time. Given the store's order number and amount, the Agent reports:
- whether the order was paid
- how it was paid
- when it was paid
It only reads and does not move money.
What you need
- Someone who can sign in to the store's NewebPay merchant account. The FDE Agent shows them where to find the store's MerchantID, HashKey and HashIV.
- End users (e.g. members of the organization) need both the order number and the amount of the order they ask about. NewebPay cannot find an order by its number alone. NewebPay also does not list orders by date.
Rollout consultation
Neweb Technologies and NewebPay are trademarks of their owner.