rabosmartpay
9 blocks in 4 groups. Open a block for its pins, an example and how it behaves.
payments
- get payment
rabosmartpayconnectionv15.0.2Reads an order as Smart Pay holds it now: was it paid, with what, and which transaction to refund. The answer that does not depend on the customer coming back or on a webhook arriving — Smart Pay asks for it as the fallback to the webhook, not as a polling loop. - list payment brands
rabosmartpayconnectionv15.0.2The payment brands configured on the webshop and whether each is active, for a checkout that offers only what will work. - create payment
rabosmartpayconnectionv15.0.2Announces an order to Rabo Smart Pay and returns the redirect url of the hosted payment page — redirect the customer there. Nothing is paid yet: the outcome comes back on the return URL, through the webhook (process webhook) and from get payment. Fulfil on the webhook or get payment, never on the return URL alone.
rabosmartpay
refunds
- create refund
rabosmartpayconnectionv15.0.2Refunds all or part of a payment transaction. Wire anidempotency keythat is stable per refund: Smart Pay answers a repeated key with the first refund instead of making a second one. - refundable details
rabosmartpayconnectionv15.0.2How much of a payment transaction can still be refunded, and until when. - get refund
rabosmartpayconnectionv15.0.2Reads one refund's status. A refund startsPENDING.
webhooks
- verify return
rabosmartpayconnectionv15.0.2Checks theorder_id,statusandsignatureSmart Pay appends to the return URL, so a customer cannot typestatus=COMPLETED. Good for choosing the page to show; fulfil on the webhook, because a customer who closes the tab never comes back. - process webhook
rabosmartpayconnectionv15.0.2Handles a Smart Pay webhook end to end. The notification carries no order, only a token, so this block verifies the notification's signature, pulls the changed orders with its token, and verifies every page of results before any of them reachesorder results. Wire the request body intopayload. Smart Pay hands each result out once: store what you act on before the endpoint answers.