CVU transaction

CVU deposits don't use a standard transaction initiation request. Instead, you provision a reusable CVU account once per shopper, show the CVU or alias in your cashier, and the shopper transfers funds from their own banking app. PXP creates the deposit when the processor notifies it, and sends you the cvu-transaction-order-executed webhook as your first and authoritative notice of the deposit.

You can submit a CVU payout in these ways:

• Payout (withdrawal), new bank account: Create a pay-by-bank transaction with apmProvider set to Cvu and intent set to Payout, and supply bankAccountNumber, bankCode, and accountType. Capture fundingData.payByBank.gatewayTokenId from the response to reuse the destination later.
• Payout (withdrawal), stored bank account: Create a payout and supply gatewaytokenid from an earlier accepted payout instead of resending bank details.

CVU supports ARS only and shoppers in Argentina (countryCode AR). Treat merchant webhooks as the authoritative final outcome. There's no hosted redirect step for CVU. Learn more about webhooks.

Use the following request to provision a reusable CVU account for a shopper. The call creates no transaction. Repeat calls for the same shopperId, merchant, and site return the same CVU account unchanged.

{
  "merchant": "MERCHANT-1",
  "site": "SITE-1",
  "shopperId": "Shopper_AR_01",
  "email": "maria.lopez@example.com",
  "firstName": "Maria",
  "lastName": "Lopez",
  "country": "AR",
  "documentType": "TaxIdNumber",
  "documentNumber": "20123456789",
  "nickName": "maria-lopez"
}

If your request is successful, you'll receive a 200 response with status set to Success. Show the cvu or alias to the shopper. Store transactionContextId if you want to update the alias later. On failure, status is Error and stateData carries the mapped fault detail.

{
  "transactionContextId": "3f6f0d0e-6d2a-4b7e-9d3c-1a2b3c4d5e6f",
  "cvu": "0000003100010000000001",
  "alias": "maria.lopez.cvu",
  "status": "Success"
}

After you display the CVU, don't call any API when the shopper deposits. Wait for the cvu-transaction-order-executed webhook, which creates and confirms the deposit. Deposit notifications may have a null merchantTransactionId because there was no merchant create call. Learn more about webhooks.

Use the following request to update the human-readable alias for a previously provisioned CVU. The CVU account number and any prior deposits are unaffected.

{
  "merchant": "MERCHANT-1",
  "site": "SITE-1",
  "alias": "maria.lopez.updated"
}

If your request is successful, you'll receive a 200 response with the same shape as the provision response and the updated alias.

{
  "transactionContextId": "3f6f0d0e-6d2a-4b7e-9d3c-1a2b3c4d5e6f",
  "cvu": "0000003100010000000001",
  "alias": "maria.lopez.updated",
  "status": "Success"
}

{
  "merchant": "MERCHANT-1",
  "site": "SITE-1",
  "merchantTransactionId": "CVU-PAYOUT-001",
  "merchantTransactionDate": "2024-01-27 08:51:02.826445+00:00",
  "transactionMethod": {
    "intent": "Payout",
    "entryType": "Ecom",
    "fundingType": "PayByBank"
  },
  "fundingData": {
    "payByBank": {
      "apmProvider": "Cvu",
      "bankAccountNumber": "0000003100010000000001",
      "bankCode": "00007",
      "accountType": "Savings"
    }
  },
  "amounts": {
    "transaction": 1400.00,
    "currencyCode": "ARS"
  },
  "shopper": {
    "id": "Shopper_AR_01",
    "firstName": "Maria",
    "lastName": "Lopez",
    "email": "maria.lopez@example.com",
    "countryCode": "AR",
    "documentType": "TaxIdNumber",
    "documentNumber": "20123456789"
  }
}

If your request is successful, you'll receive a 200 response. For a successful CVU payout initiation, expect a Pending state with no redirectUrl, plus fundingData.payByBank.paymentId and fundingData.payByBank.gatewayTokenId. providerTransactionId and fundingData.payByBank.processorPaymentId aren't on the immediate response. They appear on a later query after PXP's background status check has run.

The final outcome is delivered by a CVU merchant webhook (e.g., cvu-transaction-order-executed). Learn more about webhooks.

Always use the systemTransactionId for later PXP API calls against the same transaction. Provider payment identifiers (providerTransactionId, fundingData.payByBank.paymentId, and fundingData.payByBank.processorPaymentId) are for reconciliation and support only.

{
  "state": "Pending",
  "systemTransactionId": "2fe879cc-f99b-5747-a2bf-78a38ddcc13c",
  "merchantTransactionId": "CVU-PAYOUT-001",
  "fundingData": {
    "payByBank": {
      "apmProvider": "Cvu",
      "paymentId": "4d2e9f81-5b3c-4a7d-9e6f-1a2b3c4d5e6f",
      "gatewayTokenId": "b6e2f1a4-c3d8-4f7a-b1e9-d2c3f4a5b6c7"
    }
  }
}