# Scan to Pay Documentation

> Scan to Pay - Powered by Ukheshe is the largest QR ecosystem within South Africa.  Scan to Pay is a QR code payment solution that allows merchants and consumers to transact contactlessly. Merchants are able to create and manage static or dynamic QR codes which allow them to accept payments seamlessly. Consumers are able to make payments that are convenient, safe and secure.

Append .md to any documentation page URL to get its markdown version.

## Guides
- [What is Scan to Pay?](https://developer.scantopay.io/docs/what-is-scan-to-pay.md): South Africa's largest QR payment platform — built for banks, fintechs, PSPs, and merchants who need a single, secure, multi-channel payments backbone.
- [Choose your integration](https://developer.scantopay.io/docs/choose-your-integration.md): Pick the integration path that matches your business and jump straight to the right section.
- [Quickstart](https://developer.scantopay.io/docs/quickstart.md): Make a successful sandbox payment, end to end, in under 15 minutes.
- [Sandbox and test cards](https://developer.scantopay.io/docs/sandbox-and-test-cards.md): Everything you need to test a Scan to Pay integration end to end without touching production.
- [Authentication](https://developer.scantopay.io/docs/authentication.md): How to authenticate every Scan to Pay API request — Basic Auth, JWT Bearer, and the security model behind them.
- [Going live](https://developer.scantopay.io/docs/going-live.md): The pre-flight checklist before you flip Scan to Pay from sandbox to production.
- [Support](https://developer.scantopay.io/docs/support.md): How to reach the right Scan to Pay team, priority definitions, response times, and what to include in a support request.
- [Webhooks](https://developer.scantopay.io/docs/webhooks.md): How Scan to Pay notifies your backend when a transaction reaches a terminal state — payload, acknowledgement, retries, and recovery.
- [Signing and verifying webhooks](https://developer.scantopay.io/docs/signing-and-verifying-webhooks.md): How to decrypt and verify the encrypted webhook payload Scan to Pay sends to your endpoint — including working code samples in five languages.
- [Errors](https://developer.scantopay.io/docs/errors.md): How Scan to Pay returns errors — HTTP status codes, the platform-specific 4xx error catalogue, and how to handle each.
- [Transaction states](https://developer.scantopay.io/docs/transaction-states.md): Every state a Scan to Pay transaction can be in, what it means, and what the integrator should do.
- [ISO response codes](https://developer.scantopay.io/docs/iso-response-codes.md): Every ISO 8583 response code Scan to Pay can return from the acquiring bank, with suggested customer-facing messages.
- [Idempotency](https://developer.scantopay.io/docs/idempotency.md): How to safely retry Scan to Pay requests without creating duplicate transactions — using merchantReference as your idempotency key.
- [Rate limits](https://developer.scantopay.io/docs/rate-limits.md): What's throttled, what isn't, and the cadence guidelines you should follow to be a good API citizen.
- [QR Payments](https://developer.scantopay.io/docs/qr-payments.md): Accept QR-based payments in-store, on a counter, on a poster, or anywhere else a printed or displayed code makes sense.
- [Static QR](https://developer.scantopay.io/docs/static-qr-payments.md): One QR printed once, used many times. Best for small merchants and any acceptance setup where you can't display a fresh QR per transaction.
- [Dynamic QR](https://developer.scantopay.io/docs/dynamic-qr-payments.md): A fresh QR code per transaction, with the amount embedded. Best for POS terminals, kiosks, and any display that can show a unique QR per sale.
- [Rendering the QR](https://developer.scantopay.io/docs/rendering-qr-codes.md): Two ways to display a Scan to Pay code as a QR — use the platform's styled PNG endpoint, or render the code yourself.
- [Managing QR codes](https://developer.scantopay.io/docs/managing-qr-codes.md): Update the amount, block, unblock, edit, query, or delete a code after you've created it.
- [QR code lifecycle](https://developer.scantopay.io/docs/qr-code-lifecycle.md): Every state a Scan to Pay code can be in, the transitions between them, and what each state means for your integration.
- [QR Code Payments — business rules](https://developer.scantopay.io/docs/qr-payments-business-rules.md): The constraints, limits, and field-level rules that apply to all QR payment flows. Read once, refer back when you hit an error.
- [Ecommerce](https://developer.scantopay.io/docs/ecommerce-payments.md): Accept Scan to Pay on your online checkout — choose hosted (Bluebox) for fastest integration, or custom for full UI control.
- [Bluebox hosted checkout](https://developer.scantopay.io/docs/ecommerce-hosted-checkout.md): Redirect customers to a Scan to Pay-hosted checkout page. Fastest way to accept e-commerce payments — most of the UI is on us.
- [Hosted checkout — business rules](https://developer.scantopay.io/docs/ecommerce-hosted-checkout-business-rules.md): The constraints, field-level rules, and operational details specific to Bluebox hosted checkout.
- [Custom checkout](https://developer.scantopay.io/docs/ecommerce-custom-checkout.md): Build your own e-commerce checkout UI from end to end using the Scan to Pay API. Maximum control, more work to maintain.
- [Handling tips](https://developer.scantopay.io/docs/handling-tips.md): Two patterns for collecting tips on a Scan to Pay transaction — merchant-side or customer-prompted in the wallet.
- [Bill payment](https://developer.scantopay.io/docs/bill-payment.md): A QR printed on an invoice, statement, utility bill, traffic fine, or parking ticket. The customer scans, confirms, pays.
- [App-to-app overview](https://developer.scantopay.io/docs/app-to-app.md): The full app-to-app flow, the per-bank URL scheme convention, and the trust model that keeps your goods safe.
- [App-to-app overview](https://developer.scantopay.io/docs/app-to-app.md): The full app-to-app flow, the per-bank URL scheme convention, and the trust model that keeps your goods safe.
- [App-to-app on Android](https://developer.scantopay.io/docs/app-to-app-android.md): Launch the Scan to Pay wallet from your Android app via Intent and receive the return via your registered URL scheme.
- [App-to-app on iOS](https://developer.scantopay.io/docs/app-to-app-ios.md): Launch the Scan to Pay wallet from your iOS app via URL scheme and receive the return via your registered scheme.
- [Handling the response](https://developer.scantopay.io/docs/app-to-app-handling-response.md): What the wallet sends back to your app, how to parse it, and the trust model for treating it as a payment result.
- [USSD payment](https://developer.scantopay.io/docs/ussd-payment.md): Accept Scan to Pay payments from feature-phone customers via USSD short code. No smartphone required.
- [USSD purchase API](https://developer.scantopay.io/docs/ussd-purchase-api.md): The WIG (Wallet Initiation Gateway) endpoints for USSD-driven payments, balance queries, and card lookups.
- [Refunds and reversals](https://developer.scantopay.io/docs/refunds-and-reversals.md): Two different ways to give a customer their money back. They look the same from outside; the rules and constraints differ significantly.
- [Refunds and reversals — business rules](https://developer.scantopay.io/docs/refunds-and-reversals-business-rules.md): The constraints, eligibility rules, and error semantics for processing refunds and reversals.
- [Querying transactions](https://developer.scantopay.io/docs/querying-transactions.md): Look up the state of a transaction from your backend — when you don't have webhooks, when you missed a delivery, or when you're reconciling.
- [Querying — business rules](https://developer.scantopay.io/docs/querying-transactions-business-rules.md): The constraints, mutual-exclusivity rules, and reconciliation gotchas that govern transaction queries.
- [Merchant onboarding overview](https://developer.scantopay.io/docs/merchant-onboarding.md): The full API surface for creating and managing merchants — endpoints, auth, and the end-to-end onboarding lifecycle.
- [Merchant onboarding overview](https://developer.scantopay.io/docs/merchant-onboarding.md): The full API surface for creating and managing merchants — endpoints, auth, and the end-to-end onboarding lifecycle.
- [Acquirer flows](https://developer.scantopay.io/docs/merchant-onboarding-acquirer-flows.md): How acquiring banks load and manage merchants on the Scan to Pay platform.
- [PSP / aggregator flows](https://developer.scantopay.io/docs/merchant-onboarding-psp-flows.md): How PSPs and aggregators onboard their own merchants onto the Scan to Pay platform.
- [Onboarding business rules](https://developer.scantopay.io/docs/merchant-onboarding-business-rules.md): Credential management, notification URL handling, password rotation, audit, and other constraints that govern the onboarding API.
- [Onboarding testing](https://developer.scantopay.io/docs/merchant-onboarding-testing.md): How to test the merchant onboarding flow end-to-end before you point your production automation at it.
- [Remote API overview](https://developer.scantopay.io/docs/remote-api-overview.md): The Scan to Pay Remote API — the protocol your wallet app uses to look up QR codes, push purchases to the acquirer, and read transaction state.
- [Purchase flow](https://developer.scantopay.io/docs/remote-api-purchase-flow.md): Step-by-step Remote API call sequence — from QR scan to confirmed transaction — with sample requests and responses.
- [Remote API — business rules](https://developer.scantopay.io/docs/remote-api-business-rules.md): The constraints, validation rules, and routing logic that govern the Scan to Pay Remote API.
- [Card provisioning](https://developer.scantopay.io/docs/card-provisioning.md): Link cards and bank accounts to a wallet profile so customers don't need to re-enter card details on every payment.
- [Card provisioning — business rules](https://developer.scantopay.io/docs/card-provisioning-business-rules.md): The constraints, state-machine rules, and validation logic governing card provisioning to a wallet.
- [Converged Wallet App](https://developer.scantopay.io/docs/converged-wallet-app.md): Embed Scan to Pay's QR-payment flow directly inside your bank app — your UI, our payment engine.
- [SDK downloads](https://developer.scantopay.io/docs/in-app-sdk-downloads.md): Download the Lib Lite Android AAR, MasterPassKit iOS XCFramework, and version 1.0 demo applications.
- [Overview](https://developer.scantopay.io/docs/android-in-app-overview.md): Lib Lite — the Scan to Pay Android in-app payment SDK. What it is, what you'll need, and how the pieces fit together.
- [Installation](https://developer.scantopay.io/docs/android-in-app-installation.md): Add Lib Lite to your Android project — Gradle setup, manifest, dependencies.
- [Requesting a payment](https://developer.scantopay.io/docs/android-in-app-payments.md): Invoke the LibLiteActivity, pass a code, and handle the payment result — with sample code and a full result-code reference.
- [Pay by App button](https://developer.scantopay.io/docs/android-in-app-pay-by-app-button.md): Drop-in button that hands the customer off to their bank's app (ABSA, Standard Bank, Capitec, etc.) via a deep link.
- [Pay by Card button](https://developer.scantopay.io/docs/android-in-app-pay-by-card-button.md): Drop-in button view that launches the Lib Lite payment activity — minimal code, consistent UX.
- [Manage card](https://developer.scantopay.io/docs/android-in-app-manage-card.md): Launch the Lib Lite card-management flow standalone — let customers add or remove cards without making a purchase.
- [Pre-registration](https://developer.scantopay.io/docs/android-in-app-pre-registration.md): Optional flow to register a card before the first purchase — for a faster first checkout when you're confident the customer will pay.
- [Loading dialog](https://developer.scantopay.io/docs/android-in-app-loading-dialog.md): Show the supplied Lib Lite progress dialog while you create a code on your backend — for visual consistency with the payment flow.
- [Errors](https://developer.scantopay.io/docs/android-in-app-errors.md): Lib Lite result codes, error codes, and the OUT_LOCATION drop-off indicator — what each one means and how to respond.
- [Release notes](https://developer.scantopay.io/docs/android-in-app-changelog.md): Current release, version history, compatibility notes, and upgrade guidance for the Lib Lite Android SDK.
- [Overview](https://developer.scantopay.io/docs/ios-in-app-overview.md): MasterpassKit — the Scan to Pay iOS in-app payment SDK. What it is, what you'll need, and how the pieces fit together.
- [Installation](https://developer.scantopay.io/docs/ios-in-app-installation.md): Embed Scan to PayKit in your iOS project — framework setup and Info.plist configuration.
- [Requesting a payment](https://developer.scantopay.io/docs/ios-in-app-payments.md): Call MPScanToPay.checkout and handle the delegate callbacks — with sample Swift and the full callback reference.
- [Pay by App button](https://developer.scantopay.io/docs/ios-in-app-pay-by-app-button.md): Drop-in UIView that hands the customer off to their bank's app (ABSA, Standard Bank, Capitec, etc.) via a deep link.
- [Pay by Card button](https://developer.scantopay.io/docs/ios-in-app-pay-by-card-button.md): Drop-in UIView that launches the Scan to PayKit checkout flow — minimal code, consistent UX.
- [Manage card](https://developer.scantopay.io/docs/ios-in-app-manage-card.md): Launch the Scan to PayKit card-management flow standalone — let customers add or remove cards without making a purchase.
- [Pre-registration](https://developer.scantopay.io/docs/ios-in-app-pre-registration.md): Optional flow to register a card before the first purchase — for a faster first checkout when you're confident the customer will pay.
- [Loading dialog](https://developer.scantopay.io/docs/ios-in-app-loading-dialog.md): Show the supplied Scan to PayKit loading dialog while you create a code on your backend — for visual consistency with the checkout flow.
- [Errors](https://developer.scantopay.io/docs/ios-in-app-errors.md): The MPError enum and delegate-callback reference for Scan to PayKit.
- [Release notes](https://developer.scantopay.io/docs/ios-in-app-changelog.md): Current release, version history, compatibility notes, and upgrade guidance for the MasterPassKit iOS SDK.
- [Authentication](https://developer.scantopay.io/docs/portal-api-authentication.md): Set up Portal API access — the ROLE_REMOTE opt-in, caller-prefix routing, and credential rotation.
- [Merchant management](https://developer.scantopay.io/docs/merchant-management.md): Create, list, update, suspend, and unsuspend merchants via the Portal API — the programmatic version of the Portal's merchant management UI.
- [Notifications](https://developer.scantopay.io/docs/notifications.md): Configure webhook URLs, add Email and SMS recipients, and rotate the webhook encryption key — all programmatically.
- [API credentials](https://developer.scantopay.io/docs/api-credentials.md): Rotate a merchant's API password — the credential used to call the Remote API, Querying Transactions, and other transactional APIs.
- [Lib Lite tokens](https://developer.scantopay.io/docs/lib-lite-tokens.md): List and generate Lib Lite tokens — the API key your mobile app passes to the In-App Payments SDK.
- [Transaction lookup](https://developer.scantopay.io/docs/transaction-lookup.md): Look up a single transaction or pull batches by date range or cardholder MSISDN — for reconciliation, customer support, and reporting.
- [Transaction certificates](https://developer.scantopay.io/docs/transaction-certificates.md): Export the minimal or complete transaction certificate as a base64-encoded PDF — used as evidence in chargebacks and audits.
- [Bulk QR codes](https://developer.scantopay.io/docs/bulk-qr.md): Create QR codes in bulk for downstream printing or distribution — PSP-only, asynchronous, callback-driven.
- [PayShap management](https://developer.scantopay.io/docs/payshap-management.md): Deactivate PayShap on an existing merchant — remove PayShap from the accepted-payments list and soft-delete the PayShap config.
- [Portal API — business rules](https://developer.scantopay.io/docs/portal-api-business-rules.md): Cross-cutting rules that apply to every Portal API endpoint — authorisation, ownership, state requirements, audit logging, and error semantics.
- [Admin Portal overview](https://developer.scantopay.io/docs/admin-portal-overview.md): The Scan to Pay Portal — the web interface for Banks, PSPs, and Merchants to manage their accounts, view transactions, and configure notifications.
- [Admin Portal login](https://developer.scantopay.io/docs/admin-portal-login.md): How to register for, log in to, and recover access to the Scan to Pay Portal.
- [Customer disputes](https://developer.scantopay.io/docs/customer-disputes.md): How customer-initiated disputes flow through Scan to Pay and the parties involved in resolution.
- [Merchant query resolution](https://developer.scantopay.io/docs/merchant-query-resolution.md): How merchants raise and resolve operational queries with their acquirer and the Scan to Pay Operations team.
- [Query resolution — business rules](https://developer.scantopay.io/docs/merchant-query-resolution-business-rules.md): The constraints, ownership rules, and escalation paths that govern merchant query resolution.
- [Brand assets](https://developer.scantopay.io/docs/brand-assets.md): The Scan to Pay logo, acceptance marks, and how to request marketing collateral.

## API Reference
- [Update voucher Bin](https://developer.scantopay.io/reference/updatevoucherbininfo-1.md): Update new bin for voucher
- [Create voucher Bin](https://developer.scantopay.io/reference/createvoucherbininfo-1.md): Create new bin for voucher
- [Update Card](https://developer.scantopay.io/reference/updatecard-1.md): Update a card for a user for your wallet.
- [Card Register](https://developer.scantopay.io/reference/registercard-1.md): Add a card to a user for your wallet.
- [Send App notification and SMS](https://developer.scantopay.io/reference/sendnotificationtoclient-1.md): Send app notification to registered client of same node or SMS to the not registered client based on received MSISDN
- [List Cards](https://developer.scantopay.io/reference/cardlist-1.md): Fetch a card list for a user for your wallet.
- [Delink Card](https://developer.scantopay.io/reference/delinkcard-1.md): Delink a card from a user for your wallet.
- [Bin Lookup](https://developer.scantopay.io/reference/getbininfo-1.md): Fetch card information for a specified BIN
- [Public E-commerce checkout client payment](https://developer.scantopay.io/reference/doecommcheckoutcardpayment.md): This request is used to initiate card payment on Eclipse and get completion URL to capture card data.
- [Internal Code API - List all Client QRs](https://developer.scantopay.io/reference/getclientqr-1.md): This request gives details about all Client QR for givent clientId.
- [Internal CARD API - Link card with client alias](https://developer.scantopay.io/reference/linkcardwithalias-1.md): This request link card with specified client alias-msidn/qr.
- [Strike Purchase using originalTxId](https://developer.scantopay.io/reference/strikepurchase.md): This endpoint allows clients to strike a card using the original transaction ID (originalTxId), regardless of the card's current status.
- [Query Code](https://developer.scantopay.io/reference/query-1.md): Query a code that has been created.
- [Update Code](https://developer.scantopay.io/reference/edit-1.md): Update a previously created code. The changes will take effect immediately.
- [Delete Code](https://developer.scantopay.io/reference/deletecode-1.md): Delete a code that has been created.
- [Unblock Code](https://developer.scantopay.io/reference/unblockcode-1.md): This unblocks a blocked code. This call enables future purchases on that code.
- [Block Code](https://developer.scantopay.io/reference/blockcode-1.md): This is an API call to temporarily block a code. This prevents purchases on the code.
- [Update Code Amount](https://developer.scantopay.io/reference/registeramount-1.md): This updates only the amount for a given code. This is done generally when the code is static
- [Create Code](https://developer.scantopay.io/reference/create_1-1.md): Generate a transactional code that can then be paid for by a cardholder. This code can be represented as a QR code, transferred using NFC or manually entered into a device. The code can also be used as part of an In App payment.
- [Generate QR](https://developer.scantopay.io/reference/generateqr-1.md): This is a convenient method for an application to display a QR code. The QR code represents a transaction. Color code indicates template background color for STP QR. Where 0=Orange, 1=B&W, 2=Grey, 3=Black
- [Scanned Code](https://developer.scantopay.io/reference/scannedv2-1.md): This allows a site to query if the user has scanned the code. This is not a 100% accurate rule so it should be used only for display purposes. As an example, if you scan once it will return true but if the user decides thereafter to refresh the website/web page it will probably not show the scanned again.
- [Network Purchase - Auto network detection](https://developer.scantopay.io/reference/networkpurchaseharbour-1.md): This is a call to initiate a WIG purchase. No network parameter needed. This call has nothing to do with codes.
- [Network Purchase - Network specified](https://developer.scantopay.io/reference/networkpurchase-1.md): This is a call to initiate a Network/WIG purchase. This call has nothing to do with codes.
- [Network Code Purchase - Network Specified](https://developer.scantopay.io/reference/networkcodepurchase-1.md): This is a call to initiate a Network/WIG purchase. This call specifies a Code that wishes to be purchased.
- [Network Balance - Network specified](https://developer.scantopay.io/reference/networkbalance-1.md): This is a call to initiate a Network/WIG Balance.
- [Network Code Purchase - Auto network detection](https://developer.scantopay.io/reference/networkcodepurchaseharbour-1.md): This is a call to initiate a Network/WIG purchase. This call specifies a Code that wishes to be purchased.
- [Network Balance - Auto network detection](https://developer.scantopay.io/reference/networkbalanceharbour-1.md): This is a call to initiate a Network/WIG Balance.
- [Network Purchase Card Lookup](https://developer.scantopay.io/reference/networkpurchasecardlookup-1.md): This provides list of cards considering CNP payment type for Network purchase
- [Remote API - transactionState](https://developer.scantopay.io/reference/gettransactionstate-1.md): Fetch Transaction State
- [Remote API - transactionState](https://developer.scantopay.io/reference/gettransactionstatev3-1.md): Fetch Transaction State with some additional fields
- [Remote API - transactionHistory v2](https://developer.scantopay.io/reference/gettransactionstatev2-1.md): Fetch Transaction History for customer (Last 10)
- [Remote API - transactionHistory](https://developer.scantopay.io/reference/transactionhistory-1.md): Fetch Transaction History for user
- [Remote API - secureCodeLookup](https://developer.scantopay.io/reference/securecodelookup-1.md): The request verifies that the transaction is eligible for 3D-Secure authentication. The response will return HTML information that the integrator must then display in a web view in order to facilitate the consumer authentication process that the card issuer prescribed.
- [Remote API - secureCodeLookup](https://developer.scantopay.io/reference/securecodelookupwithcardid-1.md): The request verifies that the transaction is eligible for 3D-Secure authentication. The response will return HTML information that the integrator must then display in a web view in order to facilitate the consumer authentication process that the card issuer prescribed.
- [Remote API - purchase](https://developer.scantopay.io/reference/dopurchase-1.md): The purchase request that must be sent to initiate a 3DS transaction to the merchant's acquirer.
- [Remote API - purchaseTx](https://developer.scantopay.io/reference/dopurchasetx-1.md): The purchase request that must be sent to initiate a 3DS transaction to the merchant's acquirer.
- [Remote API - purchaseTxCardId](https://developer.scantopay.io/reference/dopurchasetxwithcardid-1.md): The purchase request that must be sent to initiate a 3DS transaction to the merchant's acquirer.
- [Remote API - purchaseCardId](https://developer.scantopay.io/reference/dopurchasewithcardid-1.md): The purchase request that must be sent to initiate a 3DS transaction to the merchant's acquirer.
- [Remote API - Code Lookup](https://developer.scantopay.io/reference/lookup-1.md): This request looks up any QR value/code supported by Scan to Pay related to the payment.
- [Remote API - Generate Transaction Id](https://developer.scantopay.io/reference/generatetxid-1.md): This request looks up any QR code/value supported by Masterpass related to the payment and returns a transactionId which must then be used on the purchaseTransactionId request to complete the payment.
- [Remote API - External notifications.](https://developer.scantopay.io/reference/processexternalnotification-1.md): To process merchant notification and callback for external transactions.
- [Remote API - Cancel Tx](https://developer.scantopay.io/reference/canceltransaction-1.md): Set a transaction state to END_CLIENT_CANCEL
- [Remote API - Bin Lookup](https://developer.scantopay.io/reference/binlookup-1.md): Fetch card information for a specified BIN
- [Remote API - menu](https://developer.scantopay.io/reference/fetchmenu-1.md): This returns the VAS menu as a JSON array. The information returned will need to be interpreted and displayed in a logical menu on the 3rd party's app/wallet so the consumer can choose what to buy/pay. Once the menu item is selected, the app/wallet's back end will need to prompt the consumer for the necessary information, should this be required.
- [Refund API Request](https://developer.scantopay.io/reference/refund-1.md): Please note the Refund rules mentioned in 1.2.3 must be adhered to for the Refund API call. A notification will be sent to the HTTP notification URL as specified for the merchant on the Scan to Pay Portal.
- [Do Refund API Request (Added Response)](https://developer.scantopay.io/reference/dorefund-1.md): Please note the Refund rules mentioned in 1.2.3 must be adhered to for the Refund API call. A notification will be sent to the HTTP notification URL as specified for the merchant on the Scan to Pay Portal.
- [Reversal API Request](https://developer.scantopay.io/reference/reverse-1.md): Please note the Reversal rules mentioned in 1.2.2 must be adhered to for the Reversal API call. A notification will be sent to the HTTP notification URL as specified for the merchant on the Scan to Pay Portal.
- [Get External Notification State](https://developer.scantopay.io/reference/processexternalnotification_1.md): Retrieves the current state of external notifications including merchant notification and callback status for a specific transaction.
- [Get status of Request Payment](https://developer.scantopay.io/reference/getpaymentrequeststatus.md): This request is used to get the status of a Pay for Me payment request.
- [Update Payment request status](https://developer.scantopay.io/reference/updatepaymentrequeststatus.md): This request is used to update the status of a Pay for Me payment request.
- [Request Payment](https://developer.scantopay.io/reference/requestpayment.md): This request is used to create a Pay for Me payment request.
- [Get Pay for Me fee for Request Payment](https://developer.scantopay.io/reference/getrequestpaymentfee.md): This request is used to get the fee applicable for Pay for Me payment request based on merchant.
- [Get Payment Request availability](https://developer.scantopay.io/reference/ispaymentrequestavailable.md): Check if a payment request is available for msisdn.
- [/app-notifications/{clientId}/update-status](https://developer.scantopay.io/reference/updatenotificationstatus.md)
- [/app-notifications/{clientId}](https://developer.scantopay.io/reference/getnotifications.md)
- [/app-notifications/{clientId}/unread-count](https://developer.scantopay.io/reference/getunreadnotificationcount.md)
- [Query Reference](https://developer.scantopay.io/reference/create-1.md): This request queries a Scan to Pay transaction and returns the status of the transaction, if available. Please note the business rules and guidelines mentioned in this document should be adhered to ensure optimal use of this function. MasterPass_Query_Notification_API_v1.1
- [Tx Refund State Lookup](https://developer.scantopay.io/reference/queryrefund-1.md): This api simply retruns the refund state of a transaction
- [Tx State Lookup](https://developer.scantopay.io/reference/create_2-1.md): This api simply returns the current state of a transaction
- [/internal/purchase/{clientId}/moneysend](https://developer.scantopay.io/reference/purchaseccpi-1.md)
- [Trigger forceKeyExchange using hsm_key_exchange_config entry by id](https://developer.scantopay.io/reference/forcekeyexchangebyid.md)
- [/diagnostic/monitor](https://developer.scantopay.io/reference/monitor.md)
- [/diagnostic/list-reports](https://developer.scantopay.io/reference/listfiles.md)
- [/diagnostic/download-report](https://developer.scantopay.io/reference/downloadreport.md)
- [/diagnostic/cleanup-reports](https://developer.scantopay.io/reference/cleanupreports.md)
- [Tx State Lookup by Qr code and amount](https://developer.scantopay.io/reference/gettxstatebyqrcode.md): This api simply returns the current state of a recent transaction by matching qr code and given amount
- [Merchant Notification V3](https://developer.scantopay.io/reference/getnotification-1.md): Create a merchant notification for Http V3