Submit card and customer info for a product
Processes a card payment for the specified product. Returns HTTP 200 for all transaction outcomes (success, decline, 3DS pending, etc.). Non-200 responses indicate a request-level failure with no transaction created.
Typical response flow
- On success:
info = "Success",subscribeSuccessand/orchargeSuccessaretrue. - On decline:
info = "Error",chargeSuccess = false,statusIdindicates the decline reason. - On 3DS required:
info = "Pending",threeDSecureIdis populated — callPOST /api/{productId}/3dsto complete. - On pre-processing error (no transaction):
infois one of"Failed","LimitReached","UserBlocked", or"None", andstatusId = 0. See theerrorfield and the Error & Decline Handling Guide.
Authorizations
This will be provided by Paysight
Path Parameters
ID of the Paysight product. This can be found at https://app.paysight.io/management/products
Body
Customer email address
Amount to charge in the transaction
Unique session identifier from Paysight. Either this or partnerSession must be provided.
Session identifier from the partner's system. Either this or paysightSession must be provided.
Customer phone number
Override to explicitly set for the transaction. It will override the Paysight logic for selecting the MID. Omit by default.
Custom metadata as key-value pairs
Paysight assigned ID of the campaign. Please set as 0 (or omit) unless you have the appropriate Paysight value
Paysight assigned ID of the traffic source / affiliate. Please set as 0 (or omit) unless you have the appropriate Paysight value
Name (or alias or your identifier) of your campaign. If campaignId is 0 and this value is provided, Paysight will auto-assign or auto-create (if new value) the campaign record
Name (or alias or your identifier) of your affiliate/traffic source. If affiliateId is 0 and this value is provided, Paysight will auto-assign or auto-create (if new value) the affiliate (traffic source) record
Sub-affiliate identifier, if applicable. This can be passed in the format 'primarysubid_secondarysubId' (or simply primarysubid if no secondary source is present). These fields are available as breakdowns in Reporting as Primary Sub ID and Secondary Sub ID
Tracking click ID from Trackhouse. Not required
User-Agent header from client request
IP address of the client
If true, will attempt a cascade, i.e. a second authorization attempt on another MID if selection conditions are met
Set to true if this transaction should use Apple Pay
Shopify-specific checkout options. Only required for Shopify integrations.
Response
Card submission result. Covers all transaction outcomes including success, all decline types, 3DS pending, already-subscribed, and pre-processing errors. Inspect info and statusId to determine the specific outcome. See the SubmitResult schema for the full statusId reference table.
Paysight session identifier
Partner session identifier
Indicates if the subscription was created successfully.
Indicates if the charge transaction was fully captured.
High-level outcome of the submission. Possible values:
Success– Transaction completed successfully.subscribeSuccessand/orchargeSuccesswill betrue.Error– Transaction-level failure. A transaction was attempted; checkstatusIdfor the decline reason.Failed– Pre-processing validation failure; no transaction was logged. Check theerrorfield.LimitReached– A rate or frequency limit was exceeded; no transaction was logged. Check theerrorfield.UserBlocked– The user, card, BIN, or email is blocked; no transaction was logged. Check theerrorfield.AlreadySubscribed– Customer is already subscribed; no new transaction was created.Pending– Awaiting 3D Secure authentication;threeDSecureIdwill be populated. CallPOST /api/{productId}/3dsto complete.RedirectRequired– A redirect is required to complete the transaction.
Success, Error, Failed, LimitReached, UserBlocked, None, AlreadySubscribed, Pending, RedirectRequired Specific error message. Interpretation depends on the accompanying info value.
When info is "Error" (statusId > 0, transaction was attempted):
This field contains the status description from the payment processor corresponding
to the statusId value. See the statusId reference tables for the full list.
When info is "Failed" (no transaction logged, statusId: 0):
"Blocked"– Request blocked at the platform level."Blocked Card"– The specific card is blocked."Invalid expiry"– CardexpiryMonthorexpiryYearis zero or missing."Invalid CVV"– CVV/CVC value is invalid or missing."Invalid CC Number"– Card number failed validation."Invalid Email"– Email address is invalid or missing."VISA cards not Supported"– VISA cards are not accepted for this product/MID."Mastercard cards not supported"– Mastercard cards are not accepted for this product/MID."Discover cards not supported"– Discover cards are not accepted for this product/MID."AMEX cards not supported"– American Express cards are not accepted for this product/MID."MAESTRO cards not supported"– Maestro cards are not accepted for this product/MID."Bin and Last4 required along with Encrypted data"–binandlastFourmust be provided when submitting encrypted card data."Specified Mid not found"– Themidfield does not match any known MID."Specified Mid does not belong to Tenant account"– Themidfield references a MID from a different tenant.
When info is "LimitReached" (no transaction logged, statusId: 0):
"CC entered too many times in quick succession"– The card number has been submitted too frequently in a short window."Email entered too many times for this product"– The email address has been used too many times for this product.
When info is "UserBlocked" (no transaction logged, statusId: 0):
"Blocked card"– Card BIN is from a blocked country."Blocked"– User is blacklisted (by email, card number, or BIN).
Email address associated with the transaction.
General message about the result. For pre-processing errors this mirrors the error field.
For 3D Secure pending flows this will be empty; check threeDSecureId instead.
Order identifier for the subscription or charge record.
Credit card descriptor that will appear on the cardholder's statement.
Merchant ID (MID number) used for the transaction.
Identifier for the 3D Secure session. Populated only when info is "Pending".
Pass this value to POST /api/{productId}/3ds to complete the authentication flow.
Null or empty in all other cases.
Unique transaction identifier from the payment processor.
Amount charged in the transaction currency.
Paysight transaction status code. 0 means no transaction was logged (pre-validation failure
or unexpected error). All other values represent a processed transaction outcome.
For the complete reference with retry guidance see the Error & Decline Handling Guide.
Successful
Issuer Declines
The issuing bank rejected the transaction. The card or account is the primary cause.
Insufficient Funds
Invalid Card Details
The card number, expiry, CVV, or holder name is invalid or failed verification.
Other / System Errors
Gateway configuration issues, platform-level blocks, duplicate detection, communication failures, and other non-issuer, non-card errors. No transaction may be retried without resolving the underlying cause.
true if the customer was subscribed even though the charge was declined
(e.g. a grace-period subscription on an insufficient-funds decline). In this
case subscribeSuccess may be true while chargeSuccess is false.
Paysight internal ID for the Merchant Account used for the transaction.
Optional portal URL defined on the Paysight Brand entry. See https://app.paysight.io/management/brands/
Bank Identification Number (first 8 digits of PAN).
Country of the BIN (ISO 3166-1 alpha-2) if available, e.g. "US".
Last 4 digits of the card number.
Electronic Commerce Indicator for 3D Secure transactions.
"02" / "05" = fully authenticated (liability shift applies).
"01" / "06" = attempted authentication.
Indicates whether the transaction was processed using a network token.
Identifier for the card-submit event. When the submit does not result in a
subscription this equals orderId. When a subscription is created (even if the
charge fails) this value differs from orderId.
Indicates if the transaction was processed as an Apple Pay payment.
Indicates if the transaction was processed as a Google Pay payment.
Raw gateway responses from each processing attempt (useful for debugging declines).
Paysight subscription ID created by this submit. 0 if no subscription was created.