Send Person to Merchant
Send Person to Merchant endpoints from Mastercard
Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.
Overview
Send Person to Merchant endpoints from Mastercard
Endpoints 15
Merchant Transfer - Funding and Payment
- POSTInitiates a Mastercard Merchant Presented QR purchase transaction by securing funds from a consumer’s account with a Funding Transaction and pushing funds to a merchant account with a Payment Transaction.
/send/#env/v1/partners/:partnerId/merchant/transferInitiates a Mastercard Merchant Presented QR purchase transaction by securing funds from a consumer’s account with a Funding Transaction and pushing funds to…
Merchant Transfer - Payment
- POSTInitiates a Mastercard Merchant Presented QR purchase transaction by pushing funds to a merchant account.
/send/#env/v1/partners/:partnerId/merchant/transfers/paymentInitiates a Mastercard Merchant Presented QR purchase transaction by pushing funds to a merchant account.
Merchant Retrieval
- GETPurpose of this service is to retrieve the Transfer resource associated with a specified transfer_reference value.
/send/#env/v1/partners/:partnerId/merchant/transfers?ref=stringPurpose of this service is to retrieve the Transfer resource associated with a specified transfer_reference value. - GETPurpose of this service is to retrieve the Transfer resource associated with the specified transfer-id.
/send/#env/v1/partners/:partnerId/merchant/transfers/:transferIdPurpose of this service is to retrieve the Transfer resource associated with the specified transfer-id.
Digital Account Reference Number
- POSTUsed to create a digital account reference number from Incontrol
/send/v1/:partnerId/digital-accountUsed to create a digital account reference number from Incontrol
Digital Account Reference Number Retrieval
- POSTUsed to retreive a digital account reference list from Incontrol
/send/v1/:partnerId/digital-account/searchUsed to retreive a digital account reference list from Incontrol
Merchant Refund
- POSTInitiates a Mastercard Merchant Presented QR Refund transaction by pushing funds from a merchant account back to the customer's account.
/send/#env/v1/partners/:partnerId/merchant/transfers/refundInitiates a Mastercard Merchant Presented QR Refund transaction by pushing funds from a merchant account back to the customer's account.
Funding
- POSTThe Funding Transaction enables the 'pull' of money from the sender's card to the Transaction Originator who is providing the Person to Merchant service. The amount that is debited from the Funding Account (sending consumer's account) will be the amount 'pushed' to the recipient via a payment transfer request. Funds can be transferred from Mastercard® or Maestro® debit card accounts. To initiate the funding transaction, users can provide the sending consumer's Primary Account Number (PAN) or a unique identifier previously mapped to the sending consumer's account.
/send/v1/partners/:partnerId/transfers/fundingThe Funding Transaction enables the 'pull' of money from the sender's card to the Transaction Originator who is providing the Person to Merchant service. The…
Funding Reversal
- POSTFunding Reversals must be submitted within 30 minutes of the funding transfer request, and should only be submitted for the following conditions: Funding Transaction must be reversed if payment transaction cannot complete successfully, i.e. the payment transaction is rejected or declined. Upon a successful reversal of a funding transaction, the refund must be credited to the sending consumer’s Funding Account.
/send/v1/partners/:partner-id/transfers/:transfer-id/transactions/:transaction-id/reversalsFunding Reversals must be submitted within 30 minutes of the funding transfer request, and should only be submitted for the following conditions: Funding…
Test Payment Notification
- POSTClient can simulate a Mastercard Merchant Presented QR Payment notification to the registered URL endpoint.
/send/v1/partners/:partnerId/events/generate/paymentClient can simulate a Mastercard Merchant Presented QR Payment notification to the registered URL endpoint.
Test Refund Notification
- POSTClient can simulate a Mastercard Merchant Presented QR Refund notification to the registered URL endpoint.
/send/v1/partners/:partnerId/events/generate/refundClient can simulate a Mastercard Merchant Presented QR Refund notification to the registered URL endpoint.
Transfer Notification Registration
- POSTThis service allows Mastercard Merchant QR originating and receiving partners to register a PAN and service provider to receive notifications on an inbound Merchant Refund or Merchant Payment Transaction.
/send/v1/partners/:partnerId/notification-registriesThis service allows Mastercard Merchant QR originating and receiving partners to register a PAN and service provider to receive notifications on an inbound… - GETThis service allows Mastercard Merchant QR originating and receiving partners to retrieve the service provider's information for a registered PAN for notifications.
/send/v1/partners/:partnerId/notification-registries/:account-reg-refThis service allows Mastercard Merchant QR originating and receiving partners to retrieve the service provider's information for a registered PAN for… - PUTThis service allows Mastercard Merchant QR originating and receiving partners to update the notitification service provider for a registered PAN.
/send/v1/partners/:partnerId/notification-registries/:account-reg-refThis service allows Mastercard Merchant QR originating and receiving partners to update the notitification service provider for a registered PAN. - DELETEThis service allows Mastercard Merchant QR originating and receiving partners to delete a registered PAN for notifications.
/send/v1/partners/:partnerId/notification-registries/:account-reg-refThis service allows Mastercard Merchant QR originating and receiving partners to delete a registered PAN for notifications.
API details
- Base URL
https://api.mastercard.com- Authentication
- None declared in the description
- Operations
- 15 operations on 13 pathsPOST 10GET 3PUT 1DELETE 1
- Main resources
- Transfer Notification Registration 4Merchant Retrieval 2Digital Account Reference Number 1Digital Account Reference Number Retrieval 1Funding 1Funding Reversal 1Merchant Refund 1Merchant Transfer - Funding and Payment 1Merchant Transfer - Payment 1Test Payment Notification 1
- Description format
- Swagger 2.0, API version
V1 - Links
- OpenAPI document
- Listed from
- APIs.guru OpenAPI Directory (CC0-1.0)
Source updated
How to test the Send Person to Merchant in Swastik Codes
- Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
- Fork it into your workspaceChoose a workspace. You get your own copy of the Send Person to Merchant collection, without the publisher's secrets.
- Add your credentialsOpen the collection's variables or an environment and enter your API key or token, if the API needs one.
- Send a requestPick an endpoint, for example “Initiates a Mastercard Merchant Presented QR purchase transaction by securing funds from a consumer’s account with a Funding Transaction and pushing funds to a merchant account with a Payment Transaction.” (POST /send/#env/v1/partners/:partnerId/merchant/transfer), and press Send. Check the response, add tests and run the whole collection with the runner.
Frequently asked questions
What is the Send Person to Merchant?
Send Person to Merchant endpoints from Mastercard It is listed under Other and has 15 endpoints.
Who publishes the Send Person to Merchant?
It is listed from Mastercard's public API description (an OpenAPI document), not published by Mastercard on Swastik Codes. Anyone who controls mastercard.com can claim the profile by adding a DNS TXT record.
What is the base URL of the Send Person to Merchant?
Requests go to https://api.mastercard.com. Endpoint paths are added to this base URL.
How do I authenticate with the Send Person to Merchant?
Its OpenAPI description does not declare an authentication scheme. Some endpoints may be open; check the provider's documentation before relying on that.
How many endpoints does the Send Person to Merchant have?
15 operations on 13 paths (10 POST, 3 GET, 1 PUT, 1 DELETE). The largest groups are Transfer Notification Registration, Merchant Retrieval, Digital Account Reference Number, Digital Account Reference Number Retrieval.
Is forking the Send Person to Merchant free?
Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.