Skip to main content

One post tagged with "Webhooks API"

View All Tags

Version 3.53.0

· 3 min read
Kristina Gauci

merchantData object in card authorisations and settlements

In January 2024, we updated the webhook events for Card Authorisations and Settlements to include the merchantCountryCode. With this release, we are further improving these webhook events by adding the merchantData object, which is already included in the Authorisation Forwarding webhook event:

WEB

The addition of the merchantData object will result in some fields being duplicated in the webhook payload. As a result, the original fields now included in the merchantData object have been marked for deprecation and will eventually be permanently removed:

WEB

We will inform you well in advance before the above deprecated fields are permanently removed and will form part of a breaking change release.

Cut-off times for physical payment card orders

Physical payment card orders are put through for fulfilment twice a week on Monday and Thursday. From a cut-off time previously 0800 GMT/BST this is now updated to 0445 GMT/BST to ensure new card orders are not put through too late for work to begin on that day.

For any details of card ordering and fulfilment on your programme, please speak to your Customer Support contact.

Self-service Embedder Portal user management

Primary administrators of Embedder product/operations teams can now add, temporarily deactivate and reactivate, and remove additional users for the Embedder Portal via a “Manage Users” screen. Please login to the Portal to test. This feature is available via the Portal UI only, not via API.

Please note “delete” does not actually delete a user, it just permanently deactivates that user credential.

Form for manually requesting change of Corporate details

When a Corporate changes any of its business details we require the Root User to confirm the changes in a form submitted via a support ticket. This ensures any changes are authorised as well as ensuring that the Corporate’s KYB information is kept up to date with Paynetics.

Examples of changes include:

  • Business name
  • Business registered address
  • Main phone number
  • Main contact details
  • Domain name used in email / allow-listed domains

If any of these details change at any time, a form submission is required.

If the Corporate wishes to change the Root User’s details or switch the Root User role to a different director/appointee then the same form should be used.

Some supporting documents are required along with the form in each case.

The End Customer should initiate a request to change Corporate details via the Embedder’s application UI or simply via front-line customer support. To request the form and get help filling it in, please open a support ticket on behalf of the End Customer.