SparkPay OpenAPI Docs
English
  • English
  • 简体中文
English
  • English
  • 简体中文
  1. Frequently Asked Questions
  • Product Introduction
  • Quick Guide
    • Integration Preparation
    • Interface Signature Description
  • Must-Read for Integration
    • Interface Rules
    • Asynchronous Notification
    • Interface Error Codes
    • Network and Currency
  • Integration Scenarios
    • Payment
    • Close Order
  • API List
    • Payment Order Creation
      POST
    • Payment Order Query
      GET
    • Payment Order Closure
      POST
    • Payment Order Creation(Pro Edition)
      POST
    • Payment Order Query(Pro Edition)
      GET
  • Frequently Asked Questions
    • Notification Related Issues
    • Redirect Failure Issues
    • Interface Error Issues
    • Test Token Acquisition/Test Network Connection
  • Integration Example
    • Interface Signature Example - PHP
    • Interface Signature Example - Postman
  • Version Notes
    • Version Notes
  1. Frequently Asked Questions

Interface Error Issues

Q: Why is the response content from the API null?#

A: Please check if the HTTP request header includes Content-Type and User-Agent. According to the Interface rules, both must not be empty when requesting the payment platform's API.

Q: Why does the API return an error saying “Request data only supports JSON format”?#

A: The API only supports data transmission in JSON format, per the Interface rules.

Q: Why does the API return an error saying “Signature verification of the API parameters failed”?#

A: Based on the Integration Preparation and API Signature Explanation, here are a few common reasons:
Reason 1: The uploaded merchant public key does not match the signature private key used in the API request. If they don't match, please re-upload the merchant public key (ensure it follows the standard public key format).
Reason 2: Check if the signing function used for the data is correct. It's highly recommended to use the signing function provided by your programming language, signing the string to be signed with SHA256 with RSA using the merchant's private key.
Reason 3: Verify if the format of the signature string in the request data is correct. Make sure to construct the signature string according to the required format and generate the request signature accordingly.
Modified at 2024-09-12 03:43:25
Previous
Redirect Failure Issues
Next
Test Token Acquisition/Test Network Connection
Built with