question

ejr avatar image
ejr asked

Xsolla request returns 404 error

I'm following a Xsolla plugin integration docs but I've hit a wall.

Xsolla is getting a 404 response to the webhook to https://{here our project id}.playfabapi.com/ThirdPartyPayments/XsollaPaymentUpdate

Request:

headers: "Accept: application/json Content-Type: application/json Content-Length: 72 Authorization: Signature 6ff284c1a446ddef1e2458a46ee5f571692161c5", 
body: { notification_type: "user_validation", user: { id: "4D0AD3825BE5E7A8" } }

Response:
httpCode: 404
message: (blank)

What's wrong with that request?

10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

·
brendan avatar image
brendan answered

Where do you see reference to an API call with that name (XsollaPaymentUpdate)? That's not part of the Xsolla purchase flow. Have a look at this tutorial (https://api.playfab.com/docs/tutorials/landing-commerce/non-receipt-payment-processing), which describes in detail how to use Xsolla as your payment provider.

3 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

ejr avatar image ejr commented ·

This request is made by a Xsolla script after client click payment button on their site. I've got this from Xsolla support.

Before that happen I use:

PlayFabClientAPI.GetPaymentToken

and then after receiving a token I open url:

https://secure.xsolla.com/paystation3/?access_token=[TOKEN]

0 Likes 0 ·
brendan avatar image brendan ejr commented ·

The endpoint is actually something you specify in your Xsolla title configuration (in their service). You should have it set to this format: https://{ {TitleID}}.playfabapi.com/ThirdPartyPayments/XsollaConfirm.

0 Likes 0 ·
ejr avatar image ejr brendan commented ·

Thanks that helped. There is still another problem with completing the purchase, but it looks like a Xsolla problem.

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.