Connect Mastercard Send Person to Merchant and Yodlee Core
Describe what you want to happen between Mastercard Send Person to Merchant and Yodlee Core in plain words. HumDay writes the program, proves it on real data, and runs it — no node graph, no field mapping, and no connector to wait for.
What HumDay can do on each side
Read from each provider’s own published API description, in their words.
Mastercard Send Person to Merchant
15 documented operations. See all Mastercard Send Person to Merchant operations
- POSTClient can simulate a Mastercard Merchant Presented QR Payment
/send/v1/partners/{partnerId}/events/generate/payment - POSTUsed to retreive a digital account reference list from Incontrol
/send/v1/{partnerId}/digital-account/search - POSTUsed to create a digital account reference number from Incontrol
/send/v1/{partnerId}/digital-account - POSTClient can simulate a Mastercard Merchant Presented QR Refund
/send/v1/partners/{partnerId}/events/generate/refund - POSTThis service allows Mastercard Merchant QR originating
/send/v1/partners/{partnerId}/notification-registries - POSTInitiates a Mastercard Merchant Presented QR purchase transaction
/send/#env/v1/partners/{partnerId}/merchant/transfer
Yodlee Core
64 documented operations. See all Yodlee Core operations
- DELETEDelete Notification Subscription
/configs/notifications/events/{eventName} - POSTSubscribe For Notification Event
/configs/notifications/events/{eventName} - PUTUpdate Notification Subscription
/configs/notifications/events/{eventName} - PUTUpdate User Details
/user - POSTAdd Manual Account
/accounts - POSTRegister User
/user/register
How a Mastercard Send Person to Merchant and Yodlee Core automation gets built
- Describe the outcome. Say what should happen — not which endpoints to call. HumDay works out which operations each side needs.
- Approve the contract. Before anything is built you see exactly what it will do in Mastercard Send Person to Merchant and Yodlee Core, and what it will never do.
- See it proven. The program runs and shows you the result before it is allowed near either live account.
- Grant access, then go live. You approve the specific operations it may use on each side — and only those.
Related integrations
- Mastercard Send Person to Merchant and OData for namespace microsoft.graph11,427 operations
- OData for namespace microsoft.graph and Yodlee Core11,476 operations
- Cloudflare and Mastercard Send Person to Merchant3,137 operations
- Cloudflare and Yodlee Core3,186 operations
- Mastercard Send Person to Merchant and NetBox859 operations
- NetBox and Yodlee Core908 operations
- GitHub and Mastercard Send Person to Merchant826 operations
- GitHub and Yodlee Core875 operations
- Mastercard Send Person to Merchant and Mist783 operations
- Mist and Yodlee Core832 operations
Questions about connecting Mastercard Send Person to Merchant and Yodlee Core
- Can Mastercard Send Person to Merchant connect with Yodlee Core?
- Yes. HumDay reads both providers' own published API descriptions and derives what each one can do, so neither side needs a hand-built connector before you can use it.
- How do I connect Mastercard Send Person to Merchant to Yodlee Core?
- Describe the outcome you want in plain words. HumDay agrees a contract with you saying exactly what it will do, writes the program, and shows you a proof run before either account is touched.
- Do I need to write code to integrate Mastercard Send Person to Merchant and Yodlee Core?
- No. There is no node graph to wire up and no field mapping to do. You say what should happen and HumDay works out which operations it needs from each side.
- What can HumDay do across Mastercard Send Person to Merchant and Yodlee Core?
- Mastercard Send Person to Merchant publishes 15 documented operations and Yodlee Core publishes 64. HumDay only ever uses the specific ones your approved contract needs.
- Is it safe to connect both accounts?
- Your credentials are stored encrypted and never appear in chat, code, or logs. Anything that writes to either Mastercard Send Person to Merchant or Yodlee Core is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for Mastercard Send Person to Merchant and Yodlee Core. Descriptions are each provider’s own words, not ours.