Notifications
Notifications
Partners should provide a valid URL so that Mondia Pay will send S2S (server to server) notifications as a POST request.
Request example
{
" uuid ": " string //{userUuid} : Unique user identifier per merchant on a specific operator "
" purchaseToken ": " string //{Purchase Token (o)} : Unique per subscription request "
" subscriptionId ": " string //{subscriptionId} : Unique per user subscription "
" subscriptionTypeId ": " string //{subscriptionTypeId} : The service id, and it is unique per service and package on each operator "
" channel ": " string //{event triggered channel} : Event triggered channel "
" event ": " string //{event[CREATE, TRIAL_START, ACTIVATE, DEACTIVATE, RENEWAL, TAGGED_FOR_CANCEL, CANCEL]} : Indicates the action taken on a specific subscription id "
" status ": " string //{Subscription status [ACTIVE, INACTIVE, PAUSED, CANCELED]} : Indicates the current status of a subscription id "
" startDate ": " string //{Subsciption start date in ISO format(eg:2020-06-01T12:53:30Z)} : Subscription start date "
" endDate ": " string //{Subsciption end date in ISO format(eg:2020-06-01T12:53:30Z)} : Subscription end date "
" price ": " {
'amount' : ' {Amount charged} : The successfully charged amount',
'currency' : ' string //{Currency code} '
} "
" trialEndDate ": " string //{Trial end date in ISO format(eg:2020-06-01T12:53:30Z)} : Free trial end date in case of free trial "
" taggerForCancellation ": " true/false : Only set with cancellation request "
" campaignId ": " string : In case the campaignId was provided with the subscription and was successfully returned and stored on our side "
" agency ": " string : In case the agency was provided with the subscription and was successfully returned and stored on our side "
" conversionId ": " string : In case the conversionId was provided with the subscription and was successfully returned and stored on our side "
" eventDateTime ": " string //{UTC date in ISO format} : Event triggering time "
}
Response
200 OK
List of Notifications
| Event | Description | |
|---|---|---|
| CREATE | Subscription is created in our system after a successful payment attempt. | |
| CREATE_INACTIVE | An inactive subscription has been created, i.e., it cannot be used for access to the service until it will be successfully renewed. | |
| CANCEL | Subscription has been cancelled with immediate effect – either by the scheduler when it expires by reaching the end date or the end of on-hold period or by some backend system, e.g.: Customer Care. | |
| TAGGED_FOR_CANCEL | Subscription has been cancelled by the customer. It is still usable until end of billing period and will be cancelled automatically upon reaching it. A new CANCEL event will be sent when the end date is reached. | |
| RENEWAL* | Subscription has been successfully renewed. | |
| ACTIVATE | An inactive subscription has been activated again. | |
| DEACTIVATE | An active subscription has been deactivated because of a failed billing – we will retry for X days, e.g.: 30 days, to re-charge the user and then activate again. After X days of on-hold (grace) period the subscription will be cancelled, and a new event will be sent. | |
| TRIAL_START | A free trial period has started (also means that a subscription is created). No separate CREATE even will be sent. | |
| CREATED_PENDING_INACTIVE** | An inactive subscription pending confirmation has been created | |
| CONFIRMATION** | A pending subscription has been confirmed |
* Sometimes we do not send renewal notifications in case of externally managed operators.
** Sometimes we send these events in case of externally managed operators