{"__v":11,"_id":"573257a99ef0fa0e0083f0dd","category":{"__v":0,"_id":"573243608b55962900f063c2","project":"573243608b55962900f063c0","version":"573243608b55962900f063c1","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-04-26T16:11:59.957Z","from_sync":false,"order":3,"slug":"express","title":"Payment Notification"},"parentDoc":null,"project":"573243608b55962900f063c0","user":"5716534c893cbe0e002d7647","version":{"__v":9,"_id":"573243608b55962900f063c1","project":"573243608b55962900f063c0","createdAt":"2016-04-19T15:51:35.494Z","releaseDate":"2016-04-19T15:51:35.494Z","categories":["573243608b55962900f063c3","573243608b55962900f063c2","573255b9ee92510e00087821","573255c0384fc70e0050ea42","573255ce9ef0fa0e0083f0d4","57334604b90dba1900b3d90c","5733474f45fc0c0e00c154da","57348e6e6a42521700a246fb","57348e79a210200e005f99e2","5734efd57e13fd17002f1129","5746204e04f2410e00a5a2e4"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-05-10T21:50:33.703Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":0,"body":"The following diagram illustrates the notification process between the Shopper, Merchant, Bank and SafetyPay.\nThis diagram includes all steps to complete a transaction; 3 and 4 represent the points where integration is required.\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/p1GOcKzSTZWwpqg8XLiW_Notification%20Process.png\",\n        \"Notification Process.png\",\n        \"618\",\n        \"284\",\n        \"#3798ce\",\n        \"\"\n      ],\n      \"caption\": \"Notification Process\",\n      \"border\": false\n    }\n  ]\n}\n[/block]\nOnce SafetyPay receives a notification from the bank that a transaction has been completed (paid by the shopper), SafetyPay will notify the Merchant via Email (optional), Automatic POST URL and/or SMS. These options must be configured in the Merchant Management Systems application (**MMS**), Section **Profile** > **Notifications**.\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/W6keBr4YSYKzHoLoy6MC_NotificationConfig.png\",\n        \"NotificationConfig.png\",\n        \"1198\",\n        \"557\",\n        \"#093768\",\n        \"\"\n      ],\n      \"border\": true\n    }\n  ]\n}\n[/block]","excerpt":"","slug":"overview-1","type":"basic","title":"Overview"}
The following diagram illustrates the notification process between the Shopper, Merchant, Bank and SafetyPay. This diagram includes all steps to complete a transaction; 3 and 4 represent the points where integration is required. [block:image] { "images": [ { "image": [ "https://files.readme.io/p1GOcKzSTZWwpqg8XLiW_Notification%20Process.png", "Notification Process.png", "618", "284", "#3798ce", "" ], "caption": "Notification Process", "border": false } ] } [/block] Once SafetyPay receives a notification from the bank that a transaction has been completed (paid by the shopper), SafetyPay will notify the Merchant via Email (optional), Automatic POST URL and/or SMS. These options must be configured in the Merchant Management Systems application (**MMS**), Section **Profile** > **Notifications**. [block:image] { "images": [ { "image": [ "https://files.readme.io/W6keBr4YSYKzHoLoy6MC_NotificationConfig.png", "NotificationConfig.png", "1198", "557", "#093768", "" ], "border": true } ] } [/block]