Skip to main content

Authorisation Forwarding

Authorisation Forwarding is an optional feature that can assist you to decide whether to accept or decline an Authorisation in real time. Weavr informs you when someone makes a card authorisation attempt by forwarding the authorisation to you after the Weavr Spend controls are processed, with additional information that will help you make a decision of the desired outcome of an authorisation.

Authorisation forwarding enables you to run your own checks on top of any spend controls you may have configured in the card profiles or on the card itself when your customers perform purchases.

Authorisation Forwarding Setup​

  1. Contact our support team to enable Authorisation Forwarding for you.

  2. Enable Authorisation Forwarding from the Card Profile and select the Default Timeout Response for the Card Profile. Default Timeout Response(Card Profile)

note

Default Timeout Response can also be set for specific cards using the Multi API in cases where a specific card needs to have a different Default Timeout Response outcome than the Default Timeout Response outcome set of the Card profile.

  1. Set the Authorisation Forwarding URL in your application settings. This URL will be the base URL where Weavr will be sending you the authorisation forwarding webhooks for you to approve or decline.
tip

Please note that you may want to change the URL before taking your application live.

  1. Setup your server endpoint by integrating with the Multi Authorisation Forwarding to receive webhooks.
EVENT{authforwarding_base_url}/managed_cards/authorisation_requestTry it
info

Weavr will wait for a response to the authorisation forwarding webhook for 1.5 seconds. If a response is not received in time, the Default Timeout Response for your application will be applied.

  1. Use the Webhooks Key from your API credentials tab in the Portal to ensure the event calls are validated.

Respond to an Authorisation Forwarding webhook​

When you receive an authorisation forwarding request on your webhook, you should respond directly to the webhook with a 200 HTTP response containing your response choice, either APPROVED or DENIED.

In case, you do not manage to send a response in 1.5 seconds, the default timeout response configuration will be used. You can set this configuration in the Weavr Portal in the card profile > Authorisation Forwarding section.

info

The default timeout response in the card profiles must be set in order to enable Authorisation forwarding.

You can also define the Default Timeout Response for a specific card by calling the Update card API and setting the authForwardingDefaultTimeoutDecision to either APPROVED or DENIED. The Default Timeout Response configured on the card will take priority over the configuration in the card profile, if it is set. The individual card default decision timeout is not mandatory.

PATCH/managed_cards/{id}Try it

Default Timeout Response​

Once an authorisation has been forwarded, Weavr expects a response within 1.5 seconds from the moment the authorisation was forwarded. In case you fail to respond to the webhook on time the default decision timeout operation will be triggered, which you set on the Card profile on the portal to either approve or decline in case a response is not received.

POSTmanaged_cards/authorisations/watchTry it