Find out how to pass metadata if you work with submerchants.

Now every documentation page is available in Markdown format. To get the content without any additional formatting, simply add .md to the URL of any page. For the landing page, add /.md.

To help developers and AI assistants work with Pike's documentation more effectively, we've prepared a dedicated llms.txt file, available at: https://developer.pikepayments.com/llms.txt.

This file provides a structured, machine-readable index of our API documentation, specifically designed for use with AI assistants, LLMs, and any tools built on top of them.

You can load this file into your AI tool or simply add it to your project's context. As a result, the AI will be able to give more accurate answers because it will be grounded directly in Pike's documentation.

Additionally, you can use the https://developer.pikepayments.com/llms-full.txt file, which includes the complete content of every page, allowing for offline responses without making extra HTTP requests.

We added information on the parameters required to process global payments.

Now the payment system logo appears as you enter the card number. Also, you can hide the Cardholder field of the widget if required.

You can now find what you need even more easily using the search panel in the top right-hand corner.

We’ve upgraded our feedback form—taking screenshots is now much easier! You can select particular areas and add captions.

Now our documentation portal is available in English: use the language selector in the top right menu.

Now you can start using our new API version.

Now the card object may contain the card_id parameter (card identifier).

Now the transaction_info object may contain the fp_message_id parameter (unique transaction identifier in FPS).

Now we can return the card BIN in the card object in responses to requests.

We have updated Pike's public keys. Please download and use them. The old keys will be supported until November 29, 2024.

We have added the errors that end users may get when interacting with the widget.

Now we return the transaction_info object with the rrn, arn, and auth_code parameters, if available. The transaction_info object is returned in the payments/payout_list, acquiring_payments/payment_list, and refunds arrays.