Add support for the custom_info object as OrderRequest argument #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As per the documentation provided by MultiSafepay (https://docs.multisafepay.com/reference/createorder), the
custom_info
object allows the inclusion of extra order-related detail fields.I've sourced the php-sdk but have not come across any indication of this feature.
To address this gap, I've taken the liberty in creating this PR to suggest some code changes.
Which addresses an approach for reported Support custom_info when creating a payment page/link #8
Type of change
Added Unit tests
Added basis unit tests to check correct implementation.
testRequestOrderRequestWithCustomInfo
on the test classOrderRequestTest.php
CustomInfoTest
to validate setting & retrieving custom info based on thecustom_1
,custom_2
&custom_3
approach described in the docs.