Skip to main content
BCP (Banco de Crédito del Perú) is one of the largest banks in Peru. With BCP as a payment method, customers get a payment code at checkout and pay it from their BCP account, in online banking or the BCP app. Payrails processes BCP through dLocal as the payment service provider (PSP). Open the dLocal guide below for its setup steps and request examples.

​
How a BCP payment works

BCP is a redirect payment method that’s paid with a code:
  1. The customer selects BCP at checkout.
  2. Payrails returns a redirect URL from the PSP, and the customer goes to the PSP’s page, which shows a BCP payment code.
  3. The customer returns to your returnInfo URL. The payment is still pending at this point.
  4. The customer pays the code in BCP online banking or the BCP app.
  5. Payrails receives the final result from the PSP and updates the payment.
Each payment is single-use: the customer pays every code on its own. Payrails captures BCP payments immediately, so a successful payment is final. To return funds, refund the payment.

​
Supported currencies and countries

BCP supports PEN (Peruvian sol) as its only presentment currency. BCP is available to customers based in:
RegionsCountries
Latin America🇵🇪 Peru

​
Integrate BCP

Choose the PSP that processes BCP for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

dLocal

BCP via dLocal

​
Check PSPs

WorkflowdLocal
Payrails SDK✔
Payrails API✔
Delayed / Manual Capture✖
Instant Capture✔
Cancel / Void✔
Refund / Reverse✔
Save Instruments✖
Merchant Initiated Transaction (MIT)✖

​
Ways to integrate BCP

  • Payrails SDK: the Web SDK shows BCP when your workflow returns it as a payment option, and redirects the customer to the page with the payment code. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with bcp as the paymentMethodCode. Each PSP guide lists the meta fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment.
Last modified on October 20, 2026