Card Auth Loop Endpoint

​

Testing in the Developer Sandbox

1. Whitelist Treasury Prime’s IP addresses in your firewall or network security rules to ensure your server can receive incoming Card Auth Loop Endpoint callbacks. Contact Treasury Prime Support for the current list of IPs to whitelist.
2. Create a new Card Auth Loop Endpoint.
3. Update the card_auth_loop_endpoint_id of the Card Product you would like to receive authorization requests for with the id of the Card Auth Loop Endpoint you created.
4. Create a new card_event.auth_request Card Simulation to mimic a card authorization taking place.
5. An HTTP POST request will be sent to the URL listed in the Card Auth Loop Endpoint containing an auth-request Card Event in the message body (example below).
6. You now have 1500 milliseconds to respond with a 200 (to approve the request) or a 402 (to reject the request).
7. If you do not respond, the default_response set in the Card Auth Loop Endpoint will take effect. Please see the warnings below.

​

Testing in Production

1. Whitelist Treasury Prime’s production IP addresses in your firewall or network security rules to ensure your server can receive incoming Card Auth Loop Endpoint callbacks. Contact Treasury Prime Support for the current list of IPs if you have not already done so.
2. Create a new Card Auth Loop Endpoint.
3. Update the card_auth_loop_endpoint_id of the Card Product you would like to receive authorization requests for with the id of the Card Auth Loop Endpoint you created.
4. Initiate authorization by swiping or submitting a virtual payment using a card issued under the Card Product from step 2.
5. An HTTP POST request will be sent to the URL listed in the Card Auth Loop Endpoint containing an auth-request Card Event in the message body (example below).
6. You now have 1500 milliseconds to respond with a 200 (to approve the request) or a 402 (to reject the request).
7. If you do not respond, the default_response set in the Card Auth Loop Endpoint will take effect. Please see the warnings below.

​

Card Auth Loop Endpoint Default Response

​

Customizing Your Response

{
  "amount": "10.00"
}

{
  "decline_reason": "082"
}

• amount (on a 200 response): A decimal string specifying a partial amount to approve. It must be positive and no greater than the requested amount; any other value is ignored and the full requested amount is approved. Note that a final balance check still takes place after your response is received, so the actual approved amount may be reduced further if funds are insufficient.
• decline_reason (on a 402 response): A string, up to 255 characters, appended to the standard decline reason and surfaced in the decline_reason field of the resulting Card Event, e.g. Card Auth Loop Endpoint Denied Request - 082.

​

Example Card Auth Loop Endpoint Callback

{
  "message_type": "auth-request",
  "amount": "25.00",
  "bank_id": "bank_treasuryprime",
  "org_id": "org_1evy4cx23n5",
  "decline_reason": null,
  "updated_at": "2022-05-26T19:43:05Z",
  "currency": "USD",
  "status": "pending",
  "id": "cnm_11h8zp29ahk22d",
  "card_id": "card_11h84t45a4d26",
  "trace_id": "aec7df65adb14c34989384d0hh44f897",
  "network": "mastercard",
  "network_created_at": null,
  "merchant": {
    "name": "Card Transaction Test 1",
    "mcc": "3501",
    "mid": "4445025949033",
    "address": {
      "city": "LAS VEGAS",
      "state": "NV",
      "postal_code": "88901",
      "country": "USA"
    }
  },
  "processor": "marqeta",
  "networkdata": null,
  "created_at": "2022-05-26T19:43:05Z",
  "atm": null
}

​

Distinguishing Original Credit Transactions (OCT)

• auth-request — Regular spending authorization (money leaving the account)
• original-credit-auth-request — OCT authorization (money arriving to the account)
• original-credit-auth-clear-request — OCT authorization and capture in one message