Skip to main content

Assign payments to stores and points of sale

Attach a storeId and/or pointOfSaleId to payments you create through the API to group transactions by store and point of sale — for reporting, analytics, and user access control. Because a point of sale belongs to a store, attaching a pointOfSaleId also associates the payment with that store.

Find each ID in the dashboard. Open Settings → Stores to read a store's storeId:

Open Settings → Points of sale to read a point of sale's pointOfSaleId:

You only need to specify these during payment creation; subsequent operations such as confirmation, capture, or refund inherit the association by default.

Assigning payments with storeId or pointOfSaleId is not available for standard integrations with e-commerce platforms such as Shopify, PrestaShop, Wix, and WooCommerce. This option is only applicable in custom implementations.

Common pitfall: scoped users and payment visibility

When you bind an authorized user to a store or point of sale, they only see payments tagged with that storeId or pointOfSaleId. Any payment created without the matching ID is invisible to that user in the dashboard. So if you use scoped users, make sure every payment carries the right storeId/pointOfSaleId — pass it in the API, or have the user create the payment in the dashboard or MONEI Pay (which inherits their assignment automatically).

Create a payment with a storeId or pointOfSaleId​

POST https://api.monei.com/v1/payments
curl --request POST 'https://api.monei.com/v1/payments' \
--header 'Authorization: pk_test_3c140607778e1217f56ccb8b50540e00' \
--header 'Content-Type: application/json' \
--data-raw '{
    "amount": 110,
    "currency": "EUR",
    "orderId": "14379133960355",
    "description": "Test Store - #14379133960355",
    "storeId": "e5f28150d9e8974c58ab5ec9c4a880f8734dcf05",
    "pointOfSaleId": "5e3f3fa8b9585e908e1b51d2c7914e61e7403078"
}'

The following parameters are required:

  • amount positive integer - Amount intended to be collected by this payment. A positive integer representing how much to charge in the (e.g., 100 cents to charge 1.00 USD)
  • currency string - Three-letter ISO currency code, in uppercase. Must be a supported currency.
  • orderId string - An order ID from your system. A unique identifier that can be used to the payment with your internal system.
  • storeId string - A unique identifier of the Store. If specified, the payment is attached to this Store.
  • pointOfSaleId string - A unique identifier of the Point of Sale. If specified, the payment is attached to this Point of Sale (and its Store).

Both are optional — pass either, both, or neither. Check all available request parameters.

Point of sale callback URL precedence​

A QR-type point of sale can define a default callback URL in its payment settings. When a payment is created with that point of sale's pointOfSaleId and you don't pass a callbackUrl, MONEI notifies the point of sale's URL when the payment completes. If you do pass a callbackUrl when creating the payment, your value takes precedence and the point-of-sale default is not applied. Handle the notification like any payment callback — verify the MONEI-Signature and return 200 OK (see Receive webhook events).

Store and point of sale configuration​

Creating stores and points of sale, payment settings (fixed amounts, required customer fields, order QR emails), QR codes and permanent payment links, and per-store IBAN are all managed in the dashboard — see stores and points of sale.