Skip to main content

Subscriptions integration

Subscriptions allow you to charge a customer on a recurring basis.


Subscription API is currently in a closed beta. If you want to use it, please contact our Support Team


1. Create a new subscription on your server.

curl --request POST '' \
--header 'Authorization: pk_test_3c140607778e1217f56ccb8b50540e00' \
--header 'Content-Type: application/json' \
--data-raw '{
"customer": {
"name": "John Doe",
"email": ""
"amount": 110,
"currency": "EUR",
"interval": "month",
"intervalCount": 1,
"description": "MoonMail Lite Monthly",
"callbackUrl": "",
"paymentCallbackUrl": ""

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 smallest currency unit (e.g., 100 cents to charge 1.00 USD)
  • currency string - Three-letter ISO currency code, in uppercase. Must be a supported currency.
  • callbackUrl string - The URL will be called each time subscription status changes.
  • paymentCallbackUrl string - The URL will be called each time subscription creates a new subscriptions.
  • interval string - Subscription interval, one of day, week, month, year
  • intervalCount number - Number of intervals between subscription subscriptions.

Check all available request parameters.

2. Activate the subscription.

curl --request POST '' \
--header 'Authorization: pk_test_3c140607778e1217f56ccb8b50540e00' \
--header 'Content-Type: application/json' \
--data-raw '{
"completeUrl": "",
"cancelUrl": ""

Check all available request parameters.

3. Redirect the customer to the redirectUrl from the response

In the response from the activate subscription request you'll get the following response:

"id": "af6029f80f5fc73a8ad2753eea0b1be0",
"amount": 110,
"currency": "EUR",
"orderId": "84370745531439",
"description": "Test Shop - #84370745531439",
"accountId": "aa9333ba-82de-400c-9ae7-087b9f8d2242",
"subscriptionId": "575bcd84-09fc-4a6e-8c4c-f88b8eb90bfa",
"livemode": false,
"status": "PENDING",
"customer": {
"email": "",
"name": "John Doe"
"nextAction": {
"type": "CONFIRM",
"mustRedirect": false,
"redirectUrl": ""
"createdAt": 1594215339

Redirect the customer to the nextAction.redirectUrl to show him the MONEI Hosted payment page.


As an alternative process you can confirm the payment by using monei.js on the client-side. Check our build a custom checkout guide.

4. Customer completes the payment

Customer enters the Card information and goes through the 3D secure verification process (is redirected to the page provided by the issuer bank of the Card for confirmation of the transaction) if required.

5. Customer is redirected back to your server

  • if customer clicks "Back to {{}}" link (you can provide in the public business details settings), s/he is redirected to cancelUrl. (Usually this url is the checkout page on your website, where the user had started a checkout process)
  • in any other case the customer is redirected to the completeUrl with payment_id and subscription_id query parameters. Use get subscription endpoint to get the subscription status.

6. An asynchronous request is sent to your server

MONEI will notify you about the payment status by sending an HTTP POST request to the callbackUrl. The request body will contain the full subscription object in JSON format.

This ensures that you get the payment status even when the customer closed the browser window or lost Internet connection.

The request also contains a MONEI-Signature header. Verify this signature to confirm that the received request is sent from MONEI.

To acknowledge the receipt of the request, your endpoint must return a 200 HTTP status code to MONEI. All other response codes, including 3xx codes, indicate to MONEI that you did not receive the event.

If MONEI does not receive a 200 HTTP status code, the notification attempt is repeated. After multiple failures to send the notification over multiple days, MONEI marks the request as failed and stops trying to send it to your endpoint.