Refactor digipay gateway

[alissn]

Description

Hi,

This PR refactors the Digipay gateway to the new version of the API. It includes the following changes:

• Changed apiPaymentUrl. Reference: 2.1. Address.
• Deleted apiPaymentUrl. the purchase method to return redirectUrl, which the user should redirect to. Reference: 2.5. Response fields.
• Fixed DocBlock of the client properties.
• Changed the hard-coded key of Guzzle with a constant from the \GuzzleHttp\RequestOptions class.
• In the verify method, pass type value from request to api url.
• Added all returned data from the gateway to the Receipt class. Reference: purchase_verify.

If further description is needed, feel free to ask!

Documents

Official Document
Persian PDF version

[khanzadimahdi]

@alissn have you tested these changes? I mean, you should have done a successful payment before merging this PR.

[alissn]

@alissn, have you tested these changes? I mean, you should have completed a successful payment before merging this PR.

In our project, we required the use this gateway but old version was not work. All responses returned the following error:

{
    "result": {
        "title": "FAILURE",
        "status": 1000,
        "message": "عملیات ناموفق بود لطفا مجددا تلاش کنید",
        "level": "BLOCKER"
    }
}

After discussing with the Digipay technical team, updating this driver became necessary.

For successful payment testing, we could only test on the staging service using this URL https://uatweb.mydigipay.info/. Obtaining a token, creating a ticket, and redirecting and verifying the purchase worked very well.

[khanzadimahdi]

I merged this PR, but this line will not work since $body not exist, please also fix this.

more insights: https://scrutinizer-ci.com/g/shetabit/multipay/inspections/0b61db53-9ab1-4a5e-8950-029ca7d50926/issues/files/src/Drivers/Digipay/Digipay.php?status=new&orderField=path&order=asc&honorSelectedPaths=0

[khanzadimahdi]

@alissn