SPEI

Home    APMs    SPEI

On this page:
Attributes
  • METHOD TYPEReal-Time Bank Transfer
  • PAYMENTS
  • PAYOUTS
  • REFUNDS
  • RECURRING

Introduction

The SPEI® APM consists of:

  • SPEI, authorized by Banco de México®, which enables users to make electronic fund transfers between bank accounts. SPEI supports regular payments (deposits).
  • STPmex, which offers technological products and services aimed at satisfying the needs of its clients in making electronic transfers. STPmex supports a multiple deposit flow and supports payouts (withdrawals).

Prerequisites and Notes

  • When a deposit request is submitted with a new user (user_token_id), a unique CLABE (Standardized Bank Code) number is generated for this specific user. The CLABE number remains the same for all future deposits with the same user. All future deposits are connected to the first request. This means that for every user, we have one request in our system but there can be many transactions associated with this user.
  • The Direct Merchant Notification (DMN) sent does NOT include other custom parameters, such as userId and customData.
  • Since the user completes the deposit offline (via his bank account), the user can submit another deposit to the same CLABE number (generated on the first deposit) without having to go to the merchant’s payment page.

Supported Countries

  • Mexico

Supported Currencies

  • MXN

Regular Payment (Deposit) Flow

Press tab to open…

Follow these steps to perform a payment using Nuvei REST API integration:

1. Generate a sessionToken

Press here for details.

2. Send a /payment Request

Perform the payment by sending a /payment request with its mandatory parameters including:

  • userTokenId
  • amount – must be greater than 0 (zero)
  • currency
  • paymentOption.alternativePaymentMethod class containing:
    • paymentMethod: “apmgw_SPEI“
  • deviceDetails class containing: ipAddress
  • billingAddress class containing: firstName, lastName,  country, email
  • userDetails class containing: firstName, lastName,  country, email
Example /payment Request
{
  "sessionToken":"<sessionToken from /getSessionToken>",
  "merchantId": "<your merchantId>",
  "merchantSiteId": "<your merchantSiteId>",
  "clientRequestId": "<unique request ID in merchant system>",
  "amount": "1000",
  "currency": "MXN",
  "userTokenId": "<unique customer identifier in merchant system>",
  "clientUniqueId": "<unique transaction ID in merchant system>",
  "paymentOption":{
    "alternativePaymentMethod":{
    "paymentMethod":"apmgw_SPEI"
    }
  },
  "deviceDetails":{
    "ipAddress":"<customer's IP address>"   
  },
  "billingAddress": {
    "firstName": "John",
    "lastName": "Smith",
    "country": "MX",
    "email":"[email protected]"
    },
  "userDetails": {
    "firstName": "John",
    "lastName": "Smith",
    "country": "MX",
    "email":"[email protected]"
    },
  "timeStamp":"<YYYYMMDDHHmmss>",
  "checksum":"<calculated checksum>"
}

After the transaction is processed, Nuvei sends a DMN that includes the result of the transaction to the URL provided in urlDetails.notificationUrl, which Nuvei recommends including in the /payment request.

Follow these steps to perform a payment using Nuvei Web SDK integration.

1. Initiate a Session

Before you can submit payment using the client-side Nuvei Web SDK, you need to send the /openOrder API call with the following mandatory parameter:

  • amount – must be greater than 0 (zero)
2. Initialize the Web SDK

Instantiate the Web SDK with the sessionToken received from the server call to /openOrder.

3. Create an APM Payment

Send a createPayment() request with its mandatory parameters including:

  • paymentOption.alternativePaymentMethod class containing:
    • paymentMethod: “apmgw_SPEI“
  • deviceDetails class containing: ipAddress
  • billingAddress class containing: firstName, lastName,  country, email
  • userDetails class containing: firstName, lastName,  country, email
Example createPayment() Request
sfc.createPayment({
  sessionToken: "<sessiontoken>",
  merchantId: "<your merchantId>",
  merchantSiteId: "<your merchantSiteId>",
  clientUniqueId: "<your clientUniqueId>",
  paymentOption: {
    alternativePaymentMethod: {
      paymentMethod: "apmgw_SPEI"
    }
  },
  deviceDetails:{
    ipAddress:"<customer's IP address>"
  },
  billingAddress: {
    firstName: "John",
    lastName: "Smith",
    country: "US",
    email: "[email protected]"
  },
   userDetails: {
    firstName: "John",
    lastName: "Smith",
    country: "US",
    email: "[email protected]"
  },
}, function(res) {
  console.log(res);
  if (res.cancelled === true) {
    example.querySelector('.token').innerText = 'cancelled';
  } else {
    example.querySelector('.token').innerText = res.transactionStatus + ' – Reference: ' + res.transactionId;
  }
  example.classList.add('submitted');
});

After the transaction is processed, Nuvei sends a DMN that includes the result of the transaction to the URL provided in urlDetails.notificationUrl, which Nuvei recommends including in the /openOrder request.

Example Payment Page Request

https://ppp-test.safecharge.com/ppp/purchase.do?merchant_id=5970183043540730700&merchant_site_id=238459&user_token=auto&user_token_id=UserID_6805031640&item_open_amount_1=false&item_min_amount_1=1&item_max_amount_1=100&item_name_1=Cashier%20Test%20product&item_amount_1=100&item_quantity_1=1&item_discount_1=0&numberofitems=1&total_tax=0&discount=0&total_amount=100.00&currency=MXN&version=4.0.0&encoding=UTF-8&first_name=test&last_name=test&address1=test&city=test&zip=123456&country=MX&phone1=123456&email=UserID_6805031640%40gmail.com&success_url=https%3A%2F%2Fhome.stefanovweb.eu%2Fresponse.php&pending_url=https%3A%2F%2Fhome.stefanovweb.eu%2Fresponse.php&error_url=https%3A%2F%2Fhome.stefanovweb.eu%2Fresponse.php&notify_url=https%3A%2F%2Fhome.stefanovweb.eu%2Fdmn.php%3Fdmnorigin%3DCheckSumCalculator&time_stamp=2024-02-04.15%3A58%3A52&checksum=385a41450364eff97fdd6355b14a1bdb&

After the transaction is processed, Nuvei sends a Direct Merchant Notification (DMN) that includes the result of the transaction to notify_url, which Nuvei recommends including in the request.

REST API

Follow these steps to perform a payment using Nuvei REST API integration:

1. Generate a sessionToken

Press here for details.

2. Send a /payment Request

Perform the payment by sending a /payment request with its mandatory parameters including:

  • userTokenId
  • amount – must be greater than 0 (zero)
  • currency
  • paymentOption.alternativePaymentMethod class containing:
    • paymentMethod: “apmgw_SPEI“
  • deviceDetails class containing: ipAddress
  • billingAddress class containing: firstName, lastName,  country, email
  • userDetails class containing: firstName, lastName,  country, email
Example /payment Request
{
  "sessionToken":"<sessionToken from /getSessionToken>",
  "merchantId": "<your merchantId>",
  "merchantSiteId": "<your merchantSiteId>",
  "clientRequestId": "<unique request ID in merchant system>",
  "amount": "1000",
  "currency": "MXN",
  "userTokenId": "<unique customer identifier in merchant system>",
  "clientUniqueId": "<unique transaction ID in merchant system>",
  "paymentOption":{
    "alternativePaymentMethod":{
    "paymentMethod":"apmgw_SPEI"
    }
  },
  "deviceDetails":{
    "ipAddress":"<customer's IP address>"   
  },
  "billingAddress": {
    "firstName": "John",
    "lastName": "Smith",
    "country": "MX",
    "email":"[email protected]"
    },
  "userDetails": {
    "firstName": "John",
    "lastName": "Smith",
    "country": "MX",
    "email":"[email protected]"
    },
  "timeStamp":"<YYYYMMDDHHmmss>",
  "checksum":"<calculated checksum>"
}

After the transaction is processed, Nuvei sends a DMN that includes the result of the transaction to the URL provided in urlDetails.notificationUrl, which Nuvei recommends including in the /payment request.

Web SDK

Follow these steps to perform a payment using Nuvei Web SDK integration.

1. Initiate a Session

Before you can submit payment using the client-side Nuvei Web SDK, you need to send the /openOrder API call with the following mandatory parameter:

  • amount – must be greater than 0 (zero)
2. Initialize the Web SDK

Instantiate the Web SDK with the sessionToken received from the server call to /openOrder.

3. Create an APM Payment

Send a createPayment() request with its mandatory parameters including:

  • paymentOption.alternativePaymentMethod class containing:
    • paymentMethod: “apmgw_SPEI“
  • deviceDetails class containing: ipAddress
  • billingAddress class containing: firstName, lastName,  country, email
  • userDetails class containing: firstName, lastName,  country, email
Example createPayment() Request
sfc.createPayment({
  sessionToken: "<sessiontoken>",
  merchantId: "<your merchantId>",
  merchantSiteId: "<your merchantSiteId>",
  clientUniqueId: "<your clientUniqueId>",
  paymentOption: {
    alternativePaymentMethod: {
      paymentMethod: "apmgw_SPEI"
    }
  },
  deviceDetails:{
    ipAddress:"<customer's IP address>"
  },
  billingAddress: {
    firstName: "John",
    lastName: "Smith",
    country: "US",
    email: "[email protected]"
  },
   userDetails: {
    firstName: "John",
    lastName: "Smith",
    country: "US",
    email: "[email protected]"
  },
}, function(res) {
  console.log(res);
  if (res.cancelled === true) {
    example.querySelector('.token').innerText = 'cancelled';
  } else {
    example.querySelector('.token').innerText = res.transactionStatus + ' – Reference: ' + res.transactionId;
  }
  example.classList.add('submitted');
});

After the transaction is processed, Nuvei sends a DMN that includes the result of the transaction to the URL provided in urlDetails.notificationUrl, which Nuvei recommends including in the /openOrder request.

Payment Page
Example Payment Page Request

https://ppp-test.safecharge.com/ppp/purchase.do?merchant_id=5970183043540730700&merchant_site_id=238459&user_token=auto&user_token_id=UserID_6805031640&item_open_amount_1=false&item_min_amount_1=1&item_max_amount_1=100&item_name_1=Cashier%20Test%20product&item_amount_1=100&item_quantity_1=1&item_discount_1=0&numberofitems=1&total_tax=0&discount=0&total_amount=100.00&currency=MXN&version=4.0.0&encoding=UTF-8&first_name=test&last_name=test&address1=test&city=test&zip=123456&country=MX&phone1=123456&email=UserID_6805031640%40gmail.com&success_url=https%3A%2F%2Fhome.stefanovweb.eu%2Fresponse.php&pending_url=https%3A%2F%2Fhome.stefanovweb.eu%2Fresponse.php&error_url=https%3A%2F%2Fhome.stefanovweb.eu%2Fresponse.php&notify_url=https%3A%2F%2Fhome.stefanovweb.eu%2Fdmn.php%3Fdmnorigin%3DCheckSumCalculator&time_stamp=2024-02-04.15%3A58%3A52&checksum=385a41450364eff97fdd6355b14a1bdb&

After the transaction is processed, Nuvei sends a Direct Merchant Notification (DMN) that includes the result of the transaction to notify_url, which Nuvei recommends including in the request.

Multi-Deposit Flow

Press tab to open…

Using Nuvei REST API integration, follow these steps:

1. Generate a sessionToken

Press here for details.

2. Send a /payment Request

Send a /payment request with its mandatory parameters including:

  • userTokenId
  • amount: “0” (zero)
  • currency
  • paymentOption.alternativePaymentMethod class containing:
    • paymentMethod: “apmgw_STPmex“
  • deviceDetails class containing: ipAddress
  • billingAddress class containing: firstName, lastName,  country, email
  • userDetails class containing: firstName, lastName,  country, email
Example /payment Request
{
  "sessionToken":"<sessionToken from /getSessionToken>",
  "merchantId": "<your merchantId>",
  "merchantSiteId": "<your merchantSiteId>",
  "clientRequestId": "<unique request ID in merchant system>",
  "amount": "0",
  "currency": "MXN",
  "userTokenId": "<unique customer identifier in merchant system>",
  "clientUniqueId": "<unique transaction ID in merchant system>",
  "paymentOption":{
    "alternativePaymentMethod":{
    "paymentMethod":"apmgw_STPmex"
    }
  },
  "deviceDetails":{
    "ipAddress":"<customer's IP address>"   
  },
  "billingAddress": {
    "firstName": "John",
    "lastName": "Smith",
    "country": "MX",
    "email":"[email protected]"
    },
  "userDetails": {
    "firstName": "John",
    "lastName": "Smith",
    "country": "MX",
    "email":"[email protected]"
    },
  "timeStamp":"<YYYYMMDDHHmmss>",
  "checksum":"<calculated checksum>"
}

After the transaction is processed, Nuvei sends a DMN that includes the result of the transaction to the URL provided in urlDetails.notificationUrl, which Nuvei recommends including in the /payment request.

Using Nuvei Web SDK integration, follow these steps.

1. Initiate a Session

Before you can submit payment using the client-side Nuvei Web SDK, you need to send the /openOrder API call with the following mandatory parameter:

  • amount: “0” (zero)
2. Initialize the Web SDK

Instantiate the Web SDK with the sessionToken received from the server call to /openOrder.

3. Create an APM Payment

Send a createPayment() request with its mandatory parameters including:

  • paymentOption.alternativePaymentMethod class containing:
    • paymentMethod: “apmgw_STPmex“
  • deviceDetails class containing: ipAddress
  • billingAddress class containing: firstName, lastName,  country, email
  • userDetails class containing: firstName, lastName,  country, email
Example createPayment() Request
sfc.createPayment({
  sessionToken: "<sessiontoken>",
  merchantId: "<your merchantId>",
  merchantSiteId: "<your merchantSiteId>",
  clientUniqueId: "<your clientUniqueId>",
  paymentOption: {
    alternativePaymentMethod: {
      paymentMethod: "apmgw_STPmex"
    }
  },
  deviceDetails:{
    ipAddress:"<customer's IP address>"
  },
  billingAddress: {
    firstName: "John",
    lastName: "Smith",
    country: "US",
    email: "[email protected]"
  },
   userDetails: {
    firstName: "John",
    lastName: "Smith",
    country: "US",
    email: "[email protected]"
  },
}, function(res) {
  console.log(res);
  if (res.cancelled === true) {
    example.querySelector('.token').innerText = 'cancelled';
  } else {
    example.querySelector('.token').innerText = res.transactionStatus + ' – Reference: ' + res.transactionId;
  }
  example.classList.add('submitted');
});

After the transaction is processed, Nuvei sends a DMN that includes the result of the transaction to the URL provided in urlDetails.notificationUrl, which Nuvei recommends including in the /openOrder request.

Example Payment Page Request

https://ppp-test.safecharge.com/ppp/purchase.do?merchant_id=5970183043540730700&merchant_site_id=238459&user_token=auto&user_token_id=UserID_6805031640&item_open_amount_1=false&item_min_amount_1=1&item_max_amount_1=100&item_name_1=Cashier%20Test%20product&item_amount_1=100&item_quantity_1=1&item_discount_1=0&numberofitems=1&total_tax=0&discount=0&total_amount=100.00&currency=MXN&version=4.0.0&encoding=UTF-8&first_name=test&last_name=test&address1=test&city=test&zip=123456&country=MX&phone1=123456&email=UserID_6805031640%40gmail.com&success_url=https%3A%2F%2Fhome.stefanovweb.eu%2Fresponse.php&pending_url=https%3A%2F%2Fhome.stefanovweb.eu%2Fresponse.php&error_url=https%3A%2F%2Fhome.stefanovweb.eu%2Fresponse.php&notify_url=https%3A%2F%2Fhome.stefanovweb.eu%2Fdmn.php%3Fdmnorigin%3DCheckSumCalculator&time_stamp=2024-02-04.15%3A58%3A52&checksum=385a41450364eff97fdd6355b14a1bdb&

After the transaction is processed, Nuvei sends a Direct Merchant Notification (DMN) that includes the result of the transaction to notify_url, which Nuvei recommends including in the request.

REST API

Using Nuvei REST API integration, follow these steps:

1. Generate a sessionToken

Press here for details.

2. Send a /payment Request

Send a /payment request with its mandatory parameters including:

  • userTokenId
  • amount: “0” (zero)
  • currency
  • paymentOption.alternativePaymentMethod class containing:
    • paymentMethod: “apmgw_STPmex“
  • deviceDetails class containing: ipAddress
  • billingAddress class containing: firstName, lastName,  country, email
  • userDetails class containing: firstName, lastName,  country, email
Example /payment Request
{
  "sessionToken":"<sessionToken from /getSessionToken>",
  "merchantId": "<your merchantId>",
  "merchantSiteId": "<your merchantSiteId>",
  "clientRequestId": "<unique request ID in merchant system>",
  "amount": "0",
  "currency": "MXN",
  "userTokenId": "<unique customer identifier in merchant system>",
  "clientUniqueId": "<unique transaction ID in merchant system>",
  "paymentOption":{
    "alternativePaymentMethod":{
    "paymentMethod":"apmgw_STPmex"
    }
  },
  "deviceDetails":{
    "ipAddress":"<customer's IP address>"   
  },
  "billingAddress": {
    "firstName": "John",
    "lastName": "Smith",
    "country": "MX",
    "email":"[email protected]"
    },
  "userDetails": {
    "firstName": "John",
    "lastName": "Smith",
    "country": "MX",
    "email":"[email protected]"
    },
  "timeStamp":"<YYYYMMDDHHmmss>",
  "checksum":"<calculated checksum>"
}

After the transaction is processed, Nuvei sends a DMN that includes the result of the transaction to the URL provided in urlDetails.notificationUrl, which Nuvei recommends including in the /payment request.

Web SDK

Using Nuvei Web SDK integration, follow these steps.

1. Initiate a Session

Before you can submit payment using the client-side Nuvei Web SDK, you need to send the /openOrder API call with the following mandatory parameter:

  • amount: “0” (zero)
2. Initialize the Web SDK

Instantiate the Web SDK with the sessionToken received from the server call to /openOrder.

3. Create an APM Payment

Send a createPayment() request with its mandatory parameters including:

  • paymentOption.alternativePaymentMethod class containing:
    • paymentMethod: “apmgw_STPmex“
  • deviceDetails class containing: ipAddress
  • billingAddress class containing: firstName, lastName,  country, email
  • userDetails class containing: firstName, lastName,  country, email
Example createPayment() Request
sfc.createPayment({
  sessionToken: "<sessiontoken>",
  merchantId: "<your merchantId>",
  merchantSiteId: "<your merchantSiteId>",
  clientUniqueId: "<your clientUniqueId>",
  paymentOption: {
    alternativePaymentMethod: {
      paymentMethod: "apmgw_STPmex"
    }
  },
  deviceDetails:{
    ipAddress:"<customer's IP address>"
  },
  billingAddress: {
    firstName: "John",
    lastName: "Smith",
    country: "US",
    email: "[email protected]"
  },
   userDetails: {
    firstName: "John",
    lastName: "Smith",
    country: "US",
    email: "[email protected]"
  },
}, function(res) {
  console.log(res);
  if (res.cancelled === true) {
    example.querySelector('.token').innerText = 'cancelled';
  } else {
    example.querySelector('.token').innerText = res.transactionStatus + ' – Reference: ' + res.transactionId;
  }
  example.classList.add('submitted');
});

After the transaction is processed, Nuvei sends a DMN that includes the result of the transaction to the URL provided in urlDetails.notificationUrl, which Nuvei recommends including in the /openOrder request.

Payment Page
Example Payment Page Request

https://ppp-test.safecharge.com/ppp/purchase.do?merchant_id=5970183043540730700&merchant_site_id=238459&user_token=auto&user_token_id=UserID_6805031640&item_open_amount_1=false&item_min_amount_1=1&item_max_amount_1=100&item_name_1=Cashier%20Test%20product&item_amount_1=100&item_quantity_1=1&item_discount_1=0&numberofitems=1&total_tax=0&discount=0&total_amount=100.00&currency=MXN&version=4.0.0&encoding=UTF-8&first_name=test&last_name=test&address1=test&city=test&zip=123456&country=MX&phone1=123456&email=UserID_6805031640%40gmail.com&success_url=https%3A%2F%2Fhome.stefanovweb.eu%2Fresponse.php&pending_url=https%3A%2F%2Fhome.stefanovweb.eu%2Fresponse.php&error_url=https%3A%2F%2Fhome.stefanovweb.eu%2Fresponse.php&notify_url=https%3A%2F%2Fhome.stefanovweb.eu%2Fdmn.php%3Fdmnorigin%3DCheckSumCalculator&time_stamp=2024-02-04.15%3A58%3A52&checksum=385a41450364eff97fdd6355b14a1bdb&

After the transaction is processed, Nuvei sends a Direct Merchant Notification (DMN) that includes the result of the transaction to notify_url, which Nuvei recommends including in the request.

Payout (Withdrawal) Flow

REST API

The following two methods can be used to process a /payout request with STPmex:

  • By collecting the customer’s bank account details using the /accountCapture method.
  • By creating a UPO, which represents the customer’s bank account details, with the /addUPOAPM method.

Press tab to open…

  1. Generate a sessionToken. Press here for details.
  2. Send an /accountCapture request that includes the following mandatory fields as shown in the example request below:
    • userTokenId – Unique customer identifier in merchant system.
    • paymentMethod: “apmgw_STPmex“
    • currencyCode: MXN
    • countryCode: MX

      Example /accountCapture Request
      {
  "sessionToken": "<sessionToken from /getSessionToken>",
  "merchantId": "<your merchantId>",
  "merchantSiteId": "<your merchantSiteId>",
  "userTokenId": "<unique customer identifier in merchant system>",
  "paymentMethod": "apmgw_STPmex",
  "currencyCode": "MXN",
  "countryCode": "MX",
}

      The request returns a redirectUrl.

      Example /accountCapture Response
      {
  "redirectUrl":"https://ppp-test.safecharge.com/ppp/acs/get.do?cccid=111&country=MX&language=en&amount=100&currency=MXN&ReturnURL=https%3a%2f%2ftest.safecharge.com%2fAPMNotificationGateway%2fSTPmex%2fSTPmexRedirectWithdrawResponse.ashx&APMTransactionID=404EE9CD3BBDDD2622BECE95DA936FF1&AccountInfo5=+",
  "userTokenId":"1810test",
  "sessionToken":"89c762b7-06c6-45f4-8517-0e335350d0e3",
  "internalRequestId":603948068,
  "status":"SUCCESS",
  "errCode":0,
  "reason":"",
  "merchantId":"221195993304907999",
  "merchantSiteId":"232618",
  "version":"1.0"
}
  3. Use redirectUrl to redirect the customer to the APM’s account details capture interface for them to enter their account details.
  4. Once the information is captured, Nuvei stores the data in a userPaymentOptionId (UPO) identifier, and sends a with the newly created userPaymentOptionId to urlDetails.notificationUrl, which Nuvei recommends including in the /accountCapture request.
  5. Send a /payout request and include the userPaymentOptionId, which contains the user’s previously stored APM account details. Press here for an example.

When relevant, it is preferable that a merchant uses the userTokenId generated from a payment transaction that was previously performed. If so, the merchant should skip to Step 2.

1. Register a userTokenId

A userTokenId is a field in the Nuvei system containing the user’s identifier in the merchant system.

If you do not have a userTokenId registered in the Nuvei system for this user, then register one by sending a /createUser request, including email, countryCode, firstName, and lastName.

Example /createUser Request
{
  "merchantId":"<your merchantId>",
  "merchantSiteId":"<your merchantSiteId>",
  "clientRequestId":"<unique request ID in merchant system>",
  "userTokenId":"<unique user identifier in merchant system>",
  "email":"[email protected]",
  "countryCode":"<2-letter ISO country code>",
  "firstName":"John",
  "lastName":"Smith",
  "timeStamp":"<YYYYMMDDHHmmss>",
  "checksum":"<calculated checksum>"
}
Example /createUser Response
{
  "userId":78403498,
  "internalRequestId":552360538,
  "status":"SUCCESS",
  "errCode":0,
  "reason":"",
  "merchantId":"2439523627382132721",
  "merchantSiteId":"224428",
  "version":"1.0",
  "clientRequestId":"20221108130736"
}

The request registers the userTokenId (userId) in the Nuvei system, which is needed to generate a userPaymentOptionId in the next step.

2. Create the UPO

Create a UPO by sending an /addUPOAPM request and include:

  • userTokenId – The unique user identifier in your system.
  • paymentMethodName: “apmgw_STPmex“
  • apmData class containing:
    • beneficiaryBank – Press here to see list of supported beneficiaryBank codes.
    • beneficiaryName
    • beneficiaryNumber
    • beneficiaryType
  • billingAddress class containing: country and email

Nuvei enables PCI compliant merchants to send debit card details instead of the CLABE number by sending the debit card number in beneficiaryNumber and setting beneficiaryType = “3“.

Please contact the Nuvei Integration Team on how to integrate this feature.

Example /addUPOAPM Request
{
  "merchantId":"<your merchantId>",
  "merchantSiteId":"<your merchantSiteId>",
  "clientRequestId":"<unique request ID in merchant system>",
  "userTokenId":"<unique customer identifier in merchant system>",
  "paymentMethodName":"apmgw_STPmex",
  "apmData": {
    "beneficiaryBank": "<supported beneficiary bank code>",
    "beneficiaryName": "John Smith",
    "beneficiaryNumber": "<CLABE number>",
    "beneficiaryType": "40"
  },
  "billingAddress":{
    "country":"MX",
    "email":"[email protected]"
  },
  "timeStamp":"<YYYYMMDDHHmmss>",
  "checksum":"<calculated checksum>"
}

The request returns an encrypted userPaymentOptionId representing the user’s APM account details.

Example /addUPOAPM Response
{
  "userPaymentOptionId":83458468,
  "internalRequestId":553078068,
  "status":"SUCCESS",
  "errCode":0,
  "reason":"",
  "merchantId":"2439523627382132721",
  "merchantSiteId":"224428",
  "version":"1.0",
  "clientRequestId":"20221109154215"
}
3. Send a /payout Request

Send a /payout request and include the userPaymentOptionId, which contains the user’s previously stored APM account details. Press here for an example.

/accountCapture
  1. Generate a sessionToken. Press here for details.
  2. Send an /accountCapture request that includes the following mandatory fields as shown in the example request below:
    • userTokenId – Unique customer identifier in merchant system.
    • paymentMethod: “apmgw_STPmex“
    • currencyCode: MXN
    • countryCode: MX

      Example /accountCapture Request
      {
  "sessionToken": "<sessionToken from /getSessionToken>",
  "merchantId": "<your merchantId>",
  "merchantSiteId": "<your merchantSiteId>",
  "userTokenId": "<unique customer identifier in merchant system>",
  "paymentMethod": "apmgw_STPmex",
  "currencyCode": "MXN",
  "countryCode": "MX",
}

      The request returns a redirectUrl.

      Example /accountCapture Response
      {
  "redirectUrl":"https://ppp-test.safecharge.com/ppp/acs/get.do?cccid=111&country=MX&language=en&amount=100&currency=MXN&ReturnURL=https%3a%2f%2ftest.safecharge.com%2fAPMNotificationGateway%2fSTPmex%2fSTPmexRedirectWithdrawResponse.ashx&APMTransactionID=404EE9CD3BBDDD2622BECE95DA936FF1&AccountInfo5=+",
  "userTokenId":"1810test",
  "sessionToken":"89c762b7-06c6-45f4-8517-0e335350d0e3",
  "internalRequestId":603948068,
  "status":"SUCCESS",
  "errCode":0,
  "reason":"",
  "merchantId":"221195993304907999",
  "merchantSiteId":"232618",
  "version":"1.0"
}
  3. Use redirectUrl to redirect the customer to the APM’s account details capture interface for them to enter their account details.
  4. Once the information is captured, Nuvei stores the data in a userPaymentOptionId (UPO) identifier, and sends a with the newly created userPaymentOptionId to urlDetails.notificationUrl, which Nuvei recommends including in the /accountCapture request.
  5. Send a /payout request and include the userPaymentOptionId, which contains the user’s previously stored APM account details. Press here for an example.
/addUPOAPM

When relevant, it is preferable that a merchant uses the userTokenId generated from a payment transaction that was previously performed. If so, the merchant should skip to Step 2.

1. Register a userTokenId

A userTokenId is a field in the Nuvei system containing the user’s identifier in the merchant system.

If you do not have a userTokenId registered in the Nuvei system for this user, then register one by sending a /createUser request, including email, countryCode, firstName, and lastName.

Example /createUser Request
{
  "merchantId":"<your merchantId>",
  "merchantSiteId":"<your merchantSiteId>",
  "clientRequestId":"<unique request ID in merchant system>",
  "userTokenId":"<unique user identifier in merchant system>",
  "email":"[email protected]",
  "countryCode":"<2-letter ISO country code>",
  "firstName":"John",
  "lastName":"Smith",
  "timeStamp":"<YYYYMMDDHHmmss>",
  "checksum":"<calculated checksum>"
}
Example /createUser Response
{
  "userId":78403498,
  "internalRequestId":552360538,
  "status":"SUCCESS",
  "errCode":0,
  "reason":"",
  "merchantId":"2439523627382132721",
  "merchantSiteId":"224428",
  "version":"1.0",
  "clientRequestId":"20221108130736"
}

The request registers the userTokenId (userId) in the Nuvei system, which is needed to generate a userPaymentOptionId in the next step.

2. Create the UPO

Create a UPO by sending an /addUPOAPM request and include:

  • userTokenId – The unique user identifier in your system.
  • paymentMethodName: “apmgw_STPmex“
  • apmData class containing:
    • beneficiaryBank – Press here to see list of supported beneficiaryBank codes.
    • beneficiaryName
    • beneficiaryNumber
    • beneficiaryType
  • billingAddress class containing: country and email

Nuvei enables PCI compliant merchants to send debit card details instead of the CLABE number by sending the debit card number in beneficiaryNumber and setting beneficiaryType = “3“.

Please contact the Nuvei Integration Team on how to integrate this feature.

Example /addUPOAPM Request
{
  "merchantId":"<your merchantId>",
  "merchantSiteId":"<your merchantSiteId>",
  "clientRequestId":"<unique request ID in merchant system>",
  "userTokenId":"<unique customer identifier in merchant system>",
  "paymentMethodName":"apmgw_STPmex",
  "apmData": {
    "beneficiaryBank": "<supported beneficiary bank code>",
    "beneficiaryName": "John Smith",
    "beneficiaryNumber": "<CLABE number>",
    "beneficiaryType": "40"
  },
  "billingAddress":{
    "country":"MX",
    "email":"[email protected]"
  },
  "timeStamp":"<YYYYMMDDHHmmss>",
  "checksum":"<calculated checksum>"
}

The request returns an encrypted userPaymentOptionId representing the user’s APM account details.

Example /addUPOAPM Response
{
  "userPaymentOptionId":83458468,
  "internalRequestId":553078068,
  "status":"SUCCESS",
  "errCode":0,
  "reason":"",
  "merchantId":"2439523627382132721",
  "merchantSiteId":"224428",
  "version":"1.0",
  "clientRequestId":"20221109154215"
}
3. Send a /payout Request

Send a /payout request and include the userPaymentOptionId, which contains the user’s previously stored APM account details. Press here for an example.

After the transaction is processed, Nuvei sends a DMN that includes the result of the transaction to the URL provided in urlDetails.notificationUrl, which Nuvei recommends including in the /payout request.

Web SDK

When performing a /payout with SPEI, the following two methods can be used to process a /payout request:

Press tab to open…

The following flow describes how to capture a user’s account details before processing a payout request using Nuvei Web SDK integration.

1. Initiate a Session

Before you can submit payment using the client-side Nuvei Web SDK, you need to send the /openOrder API call.

2. Initialize the Web SDK

Instantiate the Web SDK with the sessionToken received from the server call to /openOrder.

You can also use the showAccountCapture Web SDK feature to open the bank capture redirectUrl in a pop-up window.

Press here for more details.

3. Send an accountCapture() request

a. Send an accountCapture() request that includes the following mandatory fields (as shown in the example request below):

  • userTokenId – Unique customer identifier in merchant system.
  • paymentMethod: “apmgw_STPmex“
  • currencyCode
  • countryCode
Example accountCapture() Request
sfc.accountCapture({
  sessionToken: "<sessiontoken>",
  merchantId: "<your merchantId>",
  merchantSiteId: "<your merchantSiteId>",
  paymentMethod: "apmgw_STPmex",
  userTokenId: "<unique customer identifier in merchant system>",
  currencyCode: "MXN",
  countryCode: "MX",
  languageCode: "en",
  urlDetails:{
    successUrl:"<URL the customer is directed to after a successful transaction>",
    pendingUrl:"<URL the customer is directed to when the transaction response is pending>",
    failureUrl:"<URL the customer is directed to after an unsuccessful transaction>",
    notificationUrl:"<URL to which DMNs are sent>"
  },
sourceApplication: "WebSDK"
}, function(accountRes) {
    console.log(accountRes);
})

The request returns a redirectUrl.

Example accountCapture() Response
{
    "redirectUrl": "<redirect URL to enter account details>",
    "userTokenId": "bankCaptureUser4",
    "sessionToken": "e44a932a-e9fc-4482-a570-cf07175408e0",
    "internalRequestId": 23238261,
    "status": "SUCCESS",
    "errCode": 0,
    "reason": "",
    "merchantId": "8256777005602846935",
    "merchantSiteId": "112106",
    "version": "1.0"
}

b. Use the redirectUrl to redirect the customer to the APM’s account details interface, to enter their account details.

c. Once the information is captured, Nuvei stores the data in a UPO record, and sends a DMN with the newly created userPaymentOptionId to urlDetails.notificationUrl, which Nuvei recommends including in the /accountCapture request.

4. Send a /payout Request

Send a /payout request and include the userPaymentOptionId, which contains the user’s previously stored APM account details. Press here for an example.

When relevant, it is preferable that a merchant uses the userTokenId generated from a payment transaction that was previously performed. If so, the merchant should skip to Step 2.

1. Register a userTokenId

A userTokenId is a field in the Nuvei system containing the user’s identifier in the merchant system.

If you do not have a userTokenId registered in the Nuvei system for this user, then register one by sending a /createUser request, including email, countryCode, firstName, and lastName.

Example /createUser Request
{
  "merchantId":"<your merchantId>",
  "merchantSiteId":"<your merchantSiteId>",
  "clientRequestId":"<unique request ID in merchant system>",
  "userTokenId":"<unique user identifier in merchant system>",
  "email":"[email protected]",
  "countryCode":"<2-letter ISO country code>",
  "firstName":"John",
  "lastName":"Smith",
  "timeStamp":"<YYYYMMDDHHmmss>",
  "checksum":"<calculated checksum>"
}
Example /createUser Response
{
  "userId":78403498,
  "internalRequestId":552360538,
  "status":"SUCCESS",
  "errCode":0,
  "reason":"",
  "merchantId":"2439523627382132721",
  "merchantSiteId":"224428",
  "version":"1.0",
  "clientRequestId":"20221108130736"
}

The request registers the userTokenId (userId) in the Nuvei system, which is needed to generate a userPaymentOptionId in the next step.

2. Create the UPO

Create a UPO by sending an addApmUpo() request and include:

  • userTokenId – The unique user identifier in your system.
  • paymentMethodName: “apmgw_STPmex“
  • apmData class containing:
    • beneficiaryBank – Press here to see list of supported beneficiaryBank codes.
    • beneficiaryName
    • beneficiaryNumber
    • beneficiaryType
  • billingAddress class containing: country and email

Nuvei enables PCI compliant merchants to send debit card details instead of the CLABE number by sending the debit card number in beneficiaryNumber and setting beneficiaryType = “3“.

Please contact the Nuvei Integration Team on how to integrate this feature.

Example addApmUpo() Request
function addApmUpo() {
  sfc.addApmUpo({
    "paymentMethodName": "apmgw_STPmex",
    "apmData": {
        "beneficiaryBank": "<supported beneficiary bank code>",
        "beneficiaryName": "John Smith",
        "beneficiaryNumber": "<CLABE number>",
        "beneficiaryType": "40"
    },
     billingAddress: { // optional
       email: '[email protected]',
       country:  'MX'
    } },
    function(result) {
      console.log(result);
  })

The request returns an encrypted userPaymentOptionId representing the user’s APM account details.

Example addApmUpo() Response
{
    "result": "ADDED",
    "errCode": 0,
    "errorDescription": "",
    "userPaymentOptionId": "14958143",
    "cancelled": false
}
3. Send a /payout Request

Send a /payout request and include the userPaymentOptionId, which contains the user’s previously stored APM account details. Press here for an example.

accountCapture()

The following flow describes how to capture a user’s account details before processing a payout request using Nuvei Web SDK integration.

1. Initiate a Session

Before you can submit payment using the client-side Nuvei Web SDK, you need to send the /openOrder API call.

2. Initialize the Web SDK

Instantiate the Web SDK with the sessionToken received from the server call to /openOrder.

You can also use the showAccountCapture Web SDK feature to open the bank capture redirectUrl in a pop-up window.

Press here for more details.

3. Send an accountCapture() request

a. Send an accountCapture() request that includes the following mandatory fields (as shown in the example request below):

  • userTokenId – Unique customer identifier in merchant system.
  • paymentMethod: “apmgw_STPmex“
  • currencyCode
  • countryCode
Example accountCapture() Request
sfc.accountCapture({
  sessionToken: "<sessiontoken>",
  merchantId: "<your merchantId>",
  merchantSiteId: "<your merchantSiteId>",
  paymentMethod: "apmgw_STPmex",
  userTokenId: "<unique customer identifier in merchant system>",
  currencyCode: "MXN",
  countryCode: "MX",
  languageCode: "en",
  urlDetails:{
    successUrl:"<URL the customer is directed to after a successful transaction>",
    pendingUrl:"<URL the customer is directed to when the transaction response is pending>",
    failureUrl:"<URL the customer is directed to after an unsuccessful transaction>",
    notificationUrl:"<URL to which DMNs are sent>"
  },
sourceApplication: "WebSDK"
}, function(accountRes) {
    console.log(accountRes);
})

The request returns a redirectUrl.

Example accountCapture() Response
{
    "redirectUrl": "<redirect URL to enter account details>",
    "userTokenId": "bankCaptureUser4",
    "sessionToken": "e44a932a-e9fc-4482-a570-cf07175408e0",
    "internalRequestId": 23238261,
    "status": "SUCCESS",
    "errCode": 0,
    "reason": "",
    "merchantId": "8256777005602846935",
    "merchantSiteId": "112106",
    "version": "1.0"
}

b. Use the redirectUrl to redirect the customer to the APM’s account details interface, to enter their account details.

c. Once the information is captured, Nuvei stores the data in a UPO record, and sends a DMN with the newly created userPaymentOptionId to urlDetails.notificationUrl, which Nuvei recommends including in the /accountCapture request.

4. Send a /payout Request

Send a /payout request and include the userPaymentOptionId, which contains the user’s previously stored APM account details. Press here for an example.

addApmUpo()

When relevant, it is preferable that a merchant uses the userTokenId generated from a payment transaction that was previously performed. If so, the merchant should skip to Step 2.

1. Register a userTokenId

A userTokenId is a field in the Nuvei system containing the user’s identifier in the merchant system.

If you do not have a userTokenId registered in the Nuvei system for this user, then register one by sending a /createUser request, including email, countryCode, firstName, and lastName.

Example /createUser Request
{
  "merchantId":"<your merchantId>",
  "merchantSiteId":"<your merchantSiteId>",
  "clientRequestId":"<unique request ID in merchant system>",
  "userTokenId":"<unique user identifier in merchant system>",
  "email":"[email protected]",
  "countryCode":"<2-letter ISO country code>",
  "firstName":"John",
  "lastName":"Smith",
  "timeStamp":"<YYYYMMDDHHmmss>",
  "checksum":"<calculated checksum>"
}
Example /createUser Response
{
  "userId":78403498,
  "internalRequestId":552360538,
  "status":"SUCCESS",
  "errCode":0,
  "reason":"",
  "merchantId":"2439523627382132721",
  "merchantSiteId":"224428",
  "version":"1.0",
  "clientRequestId":"20221108130736"
}

The request registers the userTokenId (userId) in the Nuvei system, which is needed to generate a userPaymentOptionId in the next step.

2. Create the UPO

Create a UPO by sending an addApmUpo() request and include:

  • userTokenId – The unique user identifier in your system.
  • paymentMethodName: “apmgw_STPmex“
  • apmData class containing:
    • beneficiaryBank – Press here to see list of supported beneficiaryBank codes.
    • beneficiaryName
    • beneficiaryNumber
    • beneficiaryType
  • billingAddress class containing: country and email

Nuvei enables PCI compliant merchants to send debit card details instead of the CLABE number by sending the debit card number in beneficiaryNumber and setting beneficiaryType = “3“.

Please contact the Nuvei Integration Team on how to integrate this feature.

Example addApmUpo() Request
function addApmUpo() {
  sfc.addApmUpo({
    "paymentMethodName": "apmgw_STPmex",
    "apmData": {
        "beneficiaryBank": "<supported beneficiary bank code>",
        "beneficiaryName": "John Smith",
        "beneficiaryNumber": "<CLABE number>",
        "beneficiaryType": "40"
    },
     billingAddress: { // optional
       email: '[email protected]',
       country:  'MX'
    } },
    function(result) {
      console.log(result);
  })

The request returns an encrypted userPaymentOptionId representing the user’s APM account details.

Example addApmUpo() Response
{
    "result": "ADDED",
    "errCode": 0,
    "errorDescription": "",
    "userPaymentOptionId": "14958143",
    "cancelled": false
}
3. Send a /payout Request

Send a /payout request and include the userPaymentOptionId, which contains the user’s previously stored APM account details. Press here for an example.

After the transaction is processed, Nuvei sends a DMN that includes the result of the transaction to the URL provided in urlDetails.notificationUrl, which Nuvei recommends including in the /payout request.

User Experience

Regular Payment

  1. The user is redirected to a page with the generated CLABE number to which you need to transfer the funds.
  2. The user selects a bank and is redirected to the bank’s login page.
  3. The user logs in and makes the transfer.
    For the transfer to succeed, the user must transfer the correct amount and use the unique reference number. The same CLABE number is used for all future deposits for the user, while the reference number is unique per transaction.
  4. After the deposit is completed, the bank sends a notification. For example,

    As mentioned above, all future deposits associated with the same user (user_token_id) are connected to the first deposit request, which means the same CLABE number is used. Custom parameters included in the deposit request are not returned in the notifications for approved deposits.

Multi-Deposit

  1. The user is redirected to a page with either one or two generated CLABEs to which you need to transfer the funds.
    One CLABE

    Two CLABEs
  2. The user selects a bank and is redirected to the bank’s login page.
  3. The user logs in and makes the transfer.
    For the transfer to succeed, the user must transfer the correct amount and use the unique reference number. The same CLABE number is used for all future deposits for the user, while the reference number is unique per transaction.
  4. After the deposit is completed, the bank sends a notification. For example,

    As mentioned above, all future deposits associated with the same user (user_token_id) are connected to the first deposit request, which means the same CLABE number is used. Custom parameters included in the deposit request are not returned in the notifications for approved deposits.

Payout

  1. The user is redirected to an account capture page.
  2. In Account type, the user selects either CLABE or DebitCard, and then either:
    • Enters their CLABE number.
    • Enters their debit card number and selects their bank.
  3. Once the user submits the form, a withdrawal request is created.

Testing

Full flow testing is not possible in an integration environment.

Appendices

Check Order

The Check Order feature is activated on request, and allows the merchant to query STPMEX for approved deposits and retrieve additional information on these deposits such as rfcCep, urlCEP, and account holder name.

There is a service that runs in the background and picks up approved STPMEX deposits for merchants that have this setting enabled, and then performs a check order call to STP.

Example DMN
...'ppp_status=OK&Status=UPDATE&ExErrCode=0&ErrCode=0&errApmCode=0&errApmDescription=&errScCode=0&errScDescription=&Reason=&ReasonCode=0&PPP_TransactionID=31706810216&userid=&merchant_unique_id=&customData=&productId=&first_name=Cristo+rey&last_name=Rodr%C3%ADguez&email=Kris2425leah%40hotmail.com&currency=MXN&customField1=&customField2=&customField3=&customField4=&customField5=&customField6=&customField7=&customField8=&customField9=&customField10=&customField11=&customField12=&customField13=&customField14=&customField15=&invoice_id=&address1=&address2=&country=Mexico&state=&city=&zip=&phone1=&phone2=&phone3=&client_ip=&nameOnCard=&cardNumber=&bin=&noCVV=&acquirerId=&acquirerBank=STPmex+MX-PI&expMonth=&expYear=&Token=&tokenId=&AuthCode=&AvsCode=&Cvv2Reply=&shippingCountry=&shippingState=&shippingCity=&shippingAddress=&shippingZip=&shippingFirstName=&shippingLastName=&shippingPhone=&shippingCell=&shippingMail=&total_discount=0.00&total_handling=0.00&total_shipping=0.00&total_tax=0.00&buyButtonProductBundleId=&merchant_site_id=222779&merchant_status=&action=&requestVersion=&message=UPDATE&merchantLocale=&unknownParameters=&payment_method=apmgw_STPmex&ID=&merchant_id=1659611123406912420&responseTimeStamp=2022-09-19.21%3A03%3A55&buyButtonProductId=&webMasterId=&appliedPromotions=&uniqueCC=&transactionType=Sale&externalEmail=&cardCompany=&eci=&user_token_id=9e28218a-9509-4fc9-ba7c-ad7caa3ce5aa&userPaymentOptionId=1665864976&TransactionID=2130000000991852528&ExternalaccountID=646052258100011027&externalAccountDescription=account_id%3A646052258100011027&externalTransactionId=3843CP01202209191901635060&APMReferenceID=AF375F0461B5E5A1ACB364A15358A003&orderTransactionId=26437565446&totalAmount=97.00&dynamicDescriptor=WINPOT&feeAmount=&amountWithoutFee=&houseNumber=&customCurrency=&upoRegistrationDate=20220913&type=DEPOSIT&clientRequestId=&relatedTransactionId=&apmPayerInfo=%7B%22estado%22%3A0%2C%22mensaje%22%3A%22Datos+consultados+correctamente%22%2C%22respuesta%22%3A%7B%22idEF%22%3A309094374%2C%22claveRastreo%22%3A%223843CP01202209191901635060%22%2C%22conceptoPago%22%3A%22cristo+rey%22%2C%22cuentaBeneficiario%22%3A%22646052258100011027%22%2C%22cuentaOrdenante%22%3A%22072905011247815235%22%2C%22empresa%22%3A%22SAFECHARGE%22%2C%22estado%22%3A%22CCO%22%2C%22fechaOperacion%22%3A20220919%2C%22institucionContraparte%22%3A40072%2C%22institucionOperante%22%3A90646%2C%22medioEntrega%22%3A1%2C%22monto%22%3A97.00%2C%22nombreBeneficiario%22%3A%22NO+INGRESADO%22%2C%22nombreOrdenante%22%3A%22CRISTO+REY+RODRIGUEZ+JACOME%22%2C%22nombreCep%22%3Anull%2C%22rfcCep%22%3A%22SDI170928EX7%22%2C%22sello%22%3Anull%2C%22rfcCurpBeneficiario%22%3A%22No+capturado%22%2C%22referenciaNumerica%22%3A220919%2C%22rfcCurpOrdenante%22%3A%22ROJC901124DI0%22%2C%22tipoCuentaBeneficiario%22%3A40%2C%22tipoCuentaOrdenante%22%3A40%2C%22tipoPago%22%3A1%2C%22tsCaptura%22%3A1663618837274%2C%22tsLiquidacion%22%3A1663618837274%2C%22causaDevolucion%22%3Anull%2C%22urlCEP%22%3A%22https%3A%2F%2Fwww.banxico.org.mx%2Fcep%2Fgo%3Fi%3D90646%26s%3D20210302%26d%3Dq19uQPRq3sdgt6MLsir4qa56mu6GylpgypPNN85PvrHR%252BFKXInTbXIXndDh5fgMC0X3T%252FRkZSqOX3dal1ABXvY7YuAQoZIZxqnO%252Fq9ng6d0%253D%22%7D%7D&responsechecksum=ce577b633adcebaa575af42185c1aceda59871cea2f783d174e58b237d972aff&advanceResponseChecksum=826d2fbf7ba9dadcaa46abc5541cc41c18e2d4ad49d1dc9fa7aa4a0d7c5c76cc',

Merchants who choose to enable this service receive two DMNs upon the initial successful deposit of a user with this method – the first DMN with Status=APPROVED and a second DMN with Status=UPDATE, which also contains the additional information that was mentioned. It is important to note that there is a time difference between the APPROVED DMN and the UPDATE DMN.

For recurring deposits performed by the user, the merchant receives only one DMN with a final response of APPROVED or DECLINED.


Bank Codes

If the customer uses a debit card for payout, include the apmData class in the /payout as shown below:

{
  "apmData":{
    "beneficiaryBank":"40044",
    "beneficiaryName":"John Doe",
    "beneficiaryNumber":"4111111111111111",
    "beneficiaryType":"3"
  }
}

The supported codes for beneficiaryBank are presented in the table below.

BankCode
BANXICO2001
BANCOMEXT37006
BANOBRAS37009
BANJERCITO37019
NAFIN37135
BaBien37166
HIPOTECARIA FED37168
BANAMEX40002
BBVA MEXICO40012
SANTANDER40014
HSBC40021
BAJIO40030
INBURSA40036
MIFEL40042
SCOTIABANK40044
BANREGIO40058
INVEX40059
BANSI40060
AFIRME40062
BANORTE40072
BANK OF AMERICA40106
MUFG40108
JP MORGAN40110
BMONEX40112
VE POR MAS40113
AZTECA40127
AUTOFIN40128
BARCLAYS40129
COMPARTAMOS40130
MULTIVA BANCO40132
ACTINVER40133
INTERCAM BANCO40136
BANCOPPEL40137
ABC CAPITAL40138
CONSUBANCO40140
VOLKSWAGEN40141
CIBANCO40143
BBASE40145
BANKAOOL40147
PAGATODO.40148
INMOBILIARIO40150
DONDE.40151
BANCREA40152
BANCO COVALTO40154
ICBC40155
SABADELL40156
SHINHAN40157
MIZUHO BANK40158
BANK OF CHINA40159
BANCO S340160
MONEXCB90600
GBM90601
MASARI90602
VALUE90605
VECTOR90608
MULTIVA CBOLSA90613
FINAMEX90616
VALMEX90617
PROFUTURO90620
CB INTERCAM90630
CI BOLSA90631
FINCOMUN90634
NU MEXICO90638
REFORMA90642
STP90646
TACTIV CB90648
CREDICAPITAL90652
KUSPIT90653
UNAGRA90656
ASP INTEGRA OPC90659
ALTERNATIVOS90661
LIBERTAD90670
CAJA POP MEXICA90677
CRISTOBAL COLON90680
CAJA TELEFONIST90683
OPM90684
FONDO (FIRA)90685
INVERCAP90686
FOMPED90689
TESORED90703
ARCUS90706
NVIO90710
INDEVAL90902
CoDi Valida90903
SANTANDER2*90814
BANAMEX2  91802
BBVA BANCOMER2*91812
SANTANDER2*91814
HSBC2*91821
BANORTE2*91872
AZTECA2*91927
Last update iconLast modified September 2024