Request Field Mapping
How portal values and merchant values map to API fields.
This page explains the most important request fields for Factoring Decline API v1.
Pre-assigned account values
| API field | Source | Notes |
|---|---|---|
connection_id | Fixed value | Always send 1. |
campaign_id | API Credentials page | Copy Campaign ID. |
offers[].offer_id | API Credentials page | Copy one of the assigned Offer IDs. |
payment_method_id | Fixed value | Always send 1 for credit card. |
action | Fixed value | Always send process. |
Tracking fields
| API field | Value to send | Purpose |
|---|---|---|
tracking1 | Website ID from the API Credentials page. | Identifies the merchant website associated with the request. |
tracking2 | Your click ID or order reference. | Used to match postbacks to your original order. Max 255 chars; letters, digits, hyphens, underscores |
tracking3 | Original decline code. | Stores the upstream decline code. |
tracking4 | Original decline reason or message. | Stores the upstream decline reason. |
tracking5 | 4 | Product type marker for Factoring Decline v1. |
Statement Descriptor
Statement Descriptor is configured separately for each approved website.
After you create a website and it is approved, open the website settings page in the merchant portal:
https://factoring.ltvx.dev/factoring/websites
Enter the Statement Descriptor values for that website.
Do not use tracking1 as the descriptor. tracking1 is the Website ID used to identify the merchant website associated with the request.
Address fields
If same_address is true, the billing address is copied from the shipping address.
If same_address is false, send the billing fields such as bill_fname, bill_lname, bill_address1, bill_city, bill_zipcode, and bill_country.
Updated 17 days ago