Access methods for merchants to ABU program
A documented MasterCard ABU operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Access methods for merchants to ABU program.
- POSTChanges data · ABU
api.mastercard.com/v1/maws
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which MasterCard ABU operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Questions
- Can HumDay access methods for merchants to abu program in MasterCard ABU?
- Yes. This operation is published in MasterCard ABU'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 MasterCard ABU data?
- Yes — this is a POST operation, so it changes something in MasterCard ABU. 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 MasterCard ABU account.
Where this came from
Read from a published API description for MasterCard ABU at developer.mastercard.com/devzone/api/portal/swagger/automatic-billing-updater-abu. The description above is the provider’s own wording, not ours. Last published 2020-08-24.