A Value that connects an incoming sale transaction to an outbound purchase (virtual card) transaction. An ITC is generated and returned for each successful authorization associated with a Sale request and is required for each purchase request. The code can be open or closed which determines if funds may be released.
The aggregate sum of the amount for each VCC requested for a single ITC. At this time, the value of an ITC may not exceed the value of the sale.
The number of purchase transactions (virtual card requests) that will be requested in the Purchases API utilizing a single ITC. An ITC is closed when the number of virtual cards requested equals the value submitted in the Expected Payments parameter. CXP encourages using one virtual card per supplier for a seamless reconciliation process.
A void transaction ‘cancels’ a sale transaction that has not settled; cardholders may see an authorization on their card statement but will not be charged for the transaction. A return transaction refunds the full or a partial amount to a cardholder and is available after a sale transaction has settled. The CXP platform settles batches each day at 2:15 am Eastern time or 6:15 am Coordinated Universal Time (UTC) with the exception of Sunday night/Monday morning which settles at 12:15 am Eastern time or 4:15 am Coordinated Universal Time (UTC).
Yes, the CXP system is not intended for processing sale-only transactions. However, in some instances a sale-only transaction may be required, in this case, placing a zero (0) in the expected payments parameter will facilitate funds for the transaction to be released with Daily Funding. Note: The submission of a sales-only transaction may impact daily margin thresholds defined in the client agreement. If a threshold is exceeded on given day funds are not released. Refer to the client agreement for specific details.
The full card number, expiration date, and CVV number are returned in the API response and available in the CXP portal for entry into the supplier's system. Note: some suppliers and applications i.e. GDS require the input of card type along with card information to process the payment.
Once a virtual card has been requested using the Purchase API it may not be modified.
Full request body and response, including URL endpoints, used that was submitted and received.
Updated over 1 year ago