Pronamic Pay with Rabo Smart Pay WP Registry grade A. No security issues foundWP RegistryNo security issues foundOpen the reportA
Rabo Smart Pay driver for the WordPress payment processing library.
Install
Upload it under Plugins → Add New Plugin → Upload Plugin, then activate.
Install straight from GitHub with WP-CLI:
wp plugin install https://github.com/pronamic/wp-pronamic-pay-rabo-smart-pay/releases/download/v4.9.0/pronamic-pay-rabo-smart-pay.4.9.0.zipOn Packagist as wp-pay-gateways/omnikassa-2:
composer require wp-pay-gateways/omnikassa-2Pronamic Pay → Gateway → Rabo Smart Pay
Rabo Smart Pay driver for the WordPress payment processing library.
Table of contents
Status
WordPress Filters
pronamic_pay_omnikassa_2_request_args
add_filter( 'pronamic_pay_omnikassa_2_request_args', function( $args ) {
$args['timeout'] = 3600;
return $args;
} );
pronamic_pay_omnikassa_2_merchant_return_url
add_filter( 'pronamic_pay_omnikassa_2_merchant_return_url', function( $url ) {
$url = 'https://example.com/';
return $url;
} );
Errors
| Request | Response Status Code | Code | Property | Message |
|---|---|---|---|---|
gatekeeper/refresh |
HTTP/1.1 401 Unauthorized | 5001 |
errorMessage |
Full authentication is required to access this resource |
order/server/api/order |
HTTP/1.1 403 Forbidden | 5001 |
consumerMessage |
The timestamp of the order announcement is invalid |
order/server/api/order |
HTTP/1.1 422 Unprocessable Entity | 5017 |
consumerMessage |
merchantOrderId is required |
order/server/api/order |
HTTP/1.1 422 Unprocessable Entity | 5017 |
consumerMessage |
merchantReturnURL is required |
order/server/api/order |
HTTP/1.1 422 Unprocessable Entity | 5017 |
consumerMessage |
currency required and should be one of: [AUD, CAD, CHF, DKK, EUR, GBP, JPY, NOK, SEK, USD] |
order/server/api/order |
HTTP/1.1 422 Unprocessable Entity | 5017 |
consumerMessage |
order amount must be greater than zero |
Simulate Requests
Refresh
curl --request GET https://betalen.rabobank.nl/omnikassa-api/gatekeeper/refresh \
--header "Authorization: Bearer __refresh_token__" \
--connect-timeout 5 \
--max-time 5 \
--user-agent "WordPress/4.9.8; https://example.com/" \
--verbose
Order
curl --request POST https://betalen.rabobank.nl/omnikassa-api-sandbox/order/server/api/order \
--header "Authorization: Bearer __refresh_token__" \
--connect-timeout 5 \
--max-time 5 \
--user-agent "WordPress/4.9.8; https://example.com/" \
--verbose
Notification
curl --request POST "https://example.com/wp-json/pronamic-pay/omnikassa-2/v1/webhook" \
--data-binary "@tests/json/notification.json" \
--user-agent "Java/1.8.0" \
--verbose
http POST https://example.com/wp-json/pronamic-pay/omnikassa-2/v1/webhook @tests/json/notification.json User-Agent:Java/1.8.0
Event
curl --request GET https://betalen.rabobank.nl/omnikassa-api-sandbox/order/server/api/events/results/merchant.order.status.changed \
--header "Authorization: Bearer __refresh_token__" \
--connect-timeout 5 \
--max-time 5 \
--user-agent "WordPress/4.9.8; https://example.com/" \
--verbose
curl --request GET https://betalen.rabobank.nl/omnikassa-api/order/server/api/events/results/merchant.order.status.changed \
--header "Authorization: Bearer __refresh_token__" \
--connect-timeout 5 \
--max-time 5 \
--user-agent "WordPress/4.9.8; https://example.com/" \
--verbose
Webhook
The Pronamic Pay OmniKassa 2.0 gateway can handle OmniKassa 2.0 notifications via the WordPress REST API.
Route: /wp-json/pronamic-pay/omnikassa-2/v1/webhook
The WordPress REST API OmniKassa 2.0 webhook can be tested with for example cURL, see for an example the Simulate Requests section.
In principle it is not possible to view this REST API endpoint via your web browser because it is a HTTP POST method only endpoint.
However, the WordPress REST API has the option to override the HTTP method via the _method parameter.
/wp-json/pronamic-pay/omnikassa-2/v1/webhook?_method=POST
License
Releases
Newest 25 of 27 recorded releases. Each count is every asset in that release; expand a row for the breakdown.