Callback URL does not match the configured value.

How do i register a callback url for receive information on transaction information when a customer pays for services


    I test the Transfer operation. But, I still have this response: { "message": "Callback URL does not match the configured value.", "code": "INVALID_CALLBACK_URL_HOST" } X-Callback-Url =
    Posted by Hidden Mon, 04 Nov 2019 12:06:40 GMT
    Good morning, i have the same issue. Can you send me the format or the regular expression of the callback-url? Thanks!
    Posted by Hidden Fri, 22 Nov 2019 11:01:28 GMT
    Hi We have same issue here is the request format. Can you please help to identify the issue? POST HTTP/1.1 Host: Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJSMjU2In0.eyJjbGllbnRJZCI6IjdhMDllZWFkLWYwNmUtNGFmYS05ZGIwLWM3ODgyYWQ2OTlmNiIsImV4cGlyZXMiOiIyMDE5LTEyLTA0VDA3OjUyOjI1LjI3MSIsInNlc3Npb25JZCI6IjUxYTM3ZGJhLTFmZWUtNDQ1Ni1iOWE5LTUwYjVhYjBhYTI5ZCJ9.ejp6Th6hUGma8mh7E-4yA82D9Fme7UocFUkK0c_AqbOoo5skaflXQZkjhn_haO9MYjHDvsfe7oewKsg7aXERU7ixv7e6Uet3Cr9Gm-WmlWgXvX_XruDaopCxljG3HS1XoPnHiRtyyZPDxC4QeJT1AlTEkujJKE-XK0Fi-GNI5TEc9OZ3fJTtwN9sZ_eBKCQ6gvjNecW2hxfurZMjFLMxcGWeyD-b2fbDt-LF1sjsaflI8kbHkK7fTNKs1e6g1qnZvLxQbHmMusqiUlMcxXUDTO4v5cGWL2nR0WhMKZmTpFfczxu0LVqslIyywTmwB_t3Htbwc94Co_nCnZXT1YWXWA X-Callback-Url: X-Reference-Id: 7a09eead-f06e-4afa-9db0-c7882ad699f6 X-Target-Environment: sandbox Content-Type: application/json Ocp-Apim-Subscription-Key: •••••••••••••••••••••••••••••••• { "amount": "200", "currency": "EUR", "externalId": "1122321", "payer": { "partyIdType": "MSISDN", "partyId": "0545096770" }, "payerMessage": "string", "payeeNote": "string" }
    Posted by Hidden Wed, 04 Dec 2019 07:16:27 GMT
    Hello, I have the same issue with INVALID_CALLBACK_URL_HOST response. First I thought it was because I've set other host for "providerCallbackHost" when I was creating a sandbox user. So I've tried using the same host both for "providerCallbackHost" and for "X-Callback-Url" header. But I'm getting the same error response. What are other possible solutions? Should the "providerCallbackHost" be equal to "X-Callback-Url"? Regards
    Posted by Hidden Mon, 09 Dec 2019 08:35:24 GMT
    Hi, I do have the same issue. INVALID_CALLBACK_URL_HOST although same value is provided for requesttopay and create api user API. It would be great if someone from the development team could help us. My format was https://host:port/endpoint. Am I missing something? It's not encouraging if such an issue stays without a response for more than a month. Best regards
    Posted by Hidden Sun, 15 Dec 2019 01:30:56 GMT
    the callback should be what you provided when creating a user { "providerCallbackHost": "" }
    Posted by Hidden Mon, 23 Dec 2019 13:50:42 GMT
    I have the same issue and I checked (and I'm sure) that the "providerCallbackHost" value is the same as I enter for the "X-Callback-Url" I think that is simply a bug and not working in the sandbox
    Posted by Hidden Wed, 03 Mar 2021 21:55:31 GMT
    Here is the solution in the sandbox environment you don't need to provide the callback url, so for your requesttopay to work remove the X-Callback-Url header and your request will pass
    Posted by Hidden Tue, 06 Apr 2021 08:05:03 GMT
    thanks very much you safe my life
    Posted by Hidden Fri, 04 Jun 2021 09:19:56 GMT
    Thanks very much I removed the X-Callback-Url from the request header and it worked
    Posted by Hidden Fri, 20 Aug 2021 08:28:51 GMT
    That's not a solution. That's ust a hack. What's the correct way to set a callback url??? MTN support is just trash
    Posted by Hidden Tue, 18 Jan 2022 16:39:09 GMT

You're not signed in. Please sign-in to report an issue or post a comment.