As a line of credit account holder uses their account to create transactions, they're logged in LoanPro as swipes. Note the following when using this request:

Swipe information is found within the LineOfCreditSwipes object. This object is nested within the LineOfCredits entity.

This request logs that a swipe was made—it does not authorize a swipe within the auth path. Swipes are authorized via the POST Create swipe request in Secure Payments.

Swipes hold transaction information such as amount, memo, assigned Bucket, merchant information, and more. Not all transaction information is required, and we've listed a payload sample below that shows the minimum required fields.

The "rawTransactionFeed" field can be used to store metadata from the card issuer.

For an example of how swipes work within the UI, take a look at our Swipes article.

Database

For information regarding Line of Credit database tables, see the following articles:

Database – Line of Credit Swipe (line_of_credit_swipe_entity)

Database – Line of Credit Account (line_of_credit_entity)

{
    "lineOfCreditId": 50,
    "amount": "637.40",
    "bucketId": 1,
    "swipeCategoryId": 3,
    "applyDate": "2023-12-18",
    "description": "TARGET #294702",
    "cardholder": 2097,
    "merchantName": "Target",
    "rawTransactionFeed": "",
    "__ignoreWarnings": false,
    "Address": {
        "address1": "2236 S 1300 E Ste D-1",
        "state": "geo.state.UT",
        "country": "company.country.usa",
        "zipcode": "84106",
        "city": "SALT LAKE CITY"
    },
  	"metadata": {
    	"keyValue": "NewValue"
    }
}

{
    "lineOfCreditId": 50,
    "amount": "637.40",
    "bucketId": 1,
    "swipeCategoryId": 3,
    "applyDate": "2023-12-18",
    "description": "TARGET #294702",
  	"metadata": {
    	"keyValue": "NewValue"
    }
}