For AI agents: the complete documentation index is at /llms.txt, and the full text of every page is at /llms-full.txt. Most pages are also available as Markdown by adding .md to the URL.

REST API - September 11, 2025

Boarding Application

Changed

The Webhook X-GP-Signature formula has been updated as follows (only applicable for REST API partners who use Paytech credentials to authenticate):
- stringtohash = stringify (JSON body, app_Secret)
- X-GP-Signature = SHA512 (stringtohash)
- NOTE: This app_secret can now be the REST API's app_Secret if the Partner has REST API credentials, or Paytech's app_secret if the Partner has Paytech Credentials
Updates to [POST] Board Application as follows:
- The following fields are now supported:
  - pricing_profile
  - Software_name
- A partial application flow can be enabled by using the flag application_type = partial, which has been mapped in the REST API to BoardingFlow = GPIPartialApplication and BoardingApplicationType = Partial
- The below fields are now optional for partial applications only (application_type = PARTIAL):
  - Note that the following fields are still mandatory for application_type = FULL
  - legal_entity
  - active_months
  - publicly_owned
  - tax_id_reference
  - bankruptcy_history
  - political_exposure_history
  - extended_services
  - persons.citizenship_country
  - merchants.merchant_category_code
  - merchants.industry
  - merchants.goods_or_services_description
  - merchants.payment_before_delivery
  - merchants.pricing_profile
  - merchants.software_name
  - merchants.payment_methods.card.payment_processing_statistics.acceptance_history
  - merchants.payment_methods.bank_transfer.account_number
  - merchants.payment_methods.bank_transfer.bank.code

Merchants

Changed

Partners boarding to ProPay can now utilize the following two fields in the REST API:
- estimated_card_present_percentage
- estimated_card_not_present_percentage

Transactions

Changed

The REST API now supports the following transaction types in these categories:
- CP Debit Card Sales via Transit
  - Fallback Swipe
- CP Debit Card Refund via Transit
  - Swipe
  - FallBack Swipe
  - EMV
These require no new permissions
New fields must be added to the linked refund request body to support debit card refunds (See API Explorer)
REST API connects to Transit debit to process these transactions
This implementation to process CP debit card transactions is similar to CP credit card transactions
The response mapping for the amount field of Transit CP Debit transactions has been updated. Updating this mapping will allow merchants to see the actual amount authorized in the case of a partial approval

Policies

Connect

Additional Resources

REST API - September 11, 2025

Boarding Application

Merchants

Transactions