Automate Mastercard Open Banking Payments initiation

What Mastercard Open Banking Payments initiation is

Open Banking - Payments initiation service

What HumDay can do in Mastercard Open Banking Payments initiation

11 documented operations change something in Mastercard Open Banking Payments initiation.

• POSTGet list of ASPSPs/payments/aspsps
• POSTRedeem the payment/payments/sepa-credit-transfers
• POSTRedeem the payment/payments/domestic-credit-transfers
• POSTRedeem the payment/payments/cross-border-credit-transfers
• POSTGet payment status/payments/sepa-credit-transfers/payment-status
• POSTGet payment status/payments/domestic-credit-transfers/payment-status
• POSTGet payment status/payments/cross-border-credit-transfers/payment-status
• POSTExtracts the original raw consent given by the aspsp/payments/consents/raw
• POSTRequest consent initiation via redirect/payments/sepa-credit-transfers/consents
• POSTRequest consent initiation via redirect/payments/domestic-credit-transfers/consents
• POSTRequest consent initiation via redirect/payments/cross-border-credit-transfers/consents

What HumDay can read from Mastercard Open Banking Payments initiation

These are the operations a schedule or a trigger can watch.

• GETReturns the status of each connectivity provider/payments/health

How automating Mastercard Open Banking Payments initiation works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live Mastercard Open Banking Payments initiation account.
4. Grant access, then go live. You approve the specific Mastercard Open Banking Payments initiation operations it may use — and only those.

Automate Mastercard Open Banking Payments initiation with these

• MasterCard ABU1 operations
• Mastercard Bill Payment Validator1 operations
• MasterCard Bin Table Listing1 operations
• Mastercard for the Settlement Currency Rate converter3 operations
• Mastercard Locations7 operations
• Mastercard MATCH6 operations
• Mastercard MDES Customer15 operations
• Mastercard Merchant Identifier1 operations
• Mastercard Payment Account Reference Inquiry1 operations
• Mastercard Personalized Offers8 operations
• Mastercard rePower2 operations
• Mastercard Send Person to Merchant15 operations

Questions about Mastercard Open Banking Payments initiation automation

Can HumDay connect to Mastercard Open Banking Payments initiation?

Yes. HumDay reads Mastercard Open Banking Payments initiation's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 12 operations are documented.

Do I need to write code to automate Mastercard Open Banking Payments initiation?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Mastercard Open Banking Payments initiation account.

What can HumDay do in Mastercard Open Banking Payments initiation?

11 of the 12 documented operations change something in Mastercard Open Banking Payments initiation, and 1 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Mastercard Open Banking Payments initiation account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Mastercard Open Banking Payments initiation is held behind that approval.

Where this came from

The operations above are read from a published API description for Mastercard Open Banking Payments initiation at developer.mastercard.com/devzone/api/portal/swagger/open-banking-connect-payment-initiatio. Descriptions are the provider’s own words, not ours. Last published 2020-08-24.