v1

latestOpenAPI 3.0.12026-07-24310590875.6 KB
transactions

Accept or reject a transaction

Accept or reject a transaction 3D Secure (3DS) challenge.

When a transaction is created, a 3DS challenge may trigger to verify the identity of the cardholder. Use this endpoint to approve or deny the transaction. The Spend & Expense user must have the ADMIN user role to perform this operation.

Subscribe to the spend.three-ds-challenge.created event to get a webhook notification when a 3DS challenge is triggered for a transaction. See Spend & Expense 3DS challenge notification payload for more information.

See 3-D Secure - BILL Spend & Expense in the BILL Help Center to learn more about 3D Secure at BILL.

post/v3/spend/transactions/{acsTransactionId}/3ds-challenge

Path parameters

acsTransactionIdstring required

BILL-generated ID or UUID of the transaction. You receive this transaction ID in the spend.three-ds-challenge.created webhook notification.

Example:{{se_transaction_uuid}}

Headers

apiTokenstring nullable

Access token for Spend & Expense API authentication

Example:{{api_token}}

Request body

action'ACCEPT' | 'REJECT' required

3D Secure action. Set this field as ACCEPT or REJECT.

Example request

{
  "action": "ACCEPT"
}

Response

Accept or reject a transaction response

idstring

BILL-generated ID of the 3D Secure response

status'SKIPPED' | 'PENDING' | 'SENT' | 'ACCEPTED' | 'REJECTED' | 'CANCELLED' | 'TIMED_OUT' | 'FAILED' | 'UNDEFINED'

3D Secure challenge status