Skip to content
Will store the PHP SDK for Riskified
PHP
Branch: master
Clone or download

Latest commit

arungopalRF Merge pull request #61 from rich-spitkovsky-riskified/TIS-148/social-…
…login-type-amazon

add amazon to social_login_type enum
Latest commit 3e87feb Mar 27, 2020

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
sample
src/Riskified Merge pull request #61 from rich-spitkovsky-riskified/TIS-148/social-… Mar 27, 2020
.gitignore
README.md
composer.json

README.md

Riskified PHP SDK

See samples/ for examples on how to use this SDK.

Migrating to API Version 2

API Version 2 introduces new features (and breaks some old ones).

Order Webhook

This version represents a shift from data-driven order handling to multiple API endpoints, each designed for a specific purpose. These include:

  • /api/create - served by $transport->createOrder()
  • /api/update - served by $transport->updateOrder()
  • /api/submit - served by $transport->submitOrder()
  • /api/refund - served by $transport->refundOrder()
  • /api/cancel - served by $transport->cancelOrder()

Refer to the online documentation for more details. When migrating from version 1, you'll need to separate the different calls to Riskified's API to support this new process.

Decision Notifications

Constructor $headers argument format

The format of the $headers argument when constructing a new Riskified\DecisionNotification\Notification instance has changed. The constructor now expects an associative array of all the HTTP headers of the request, and not a flat array of strings, as in previous versions of this SDK.

This change should simplify integration since the argument now follows the format of the return value of the popular PHP/Apache function getallheaders().

API v2 payload format

Notification requests in API version 2 now contain a JSON encoded payload which is more flexible and easily extended.

If you are already using the Notification class in version 1, there are no additional actions required to support the migration to JSON, as this SDK handles the new data format seamlessly.

You can’t perform that action at this time.