MyBank

Integrate MyBank and allow merchants to get a direct link between a consumer's online bank account and their own. This eliminates the need to collect and store personal data.

Payment Method Properties

Available country codesIT, BE,PT,ES
Processing (Presentation) currenciesEUR
Settlement currenciesEUR
Consumer currenciesEUR
Channel member tagmybank
Scheme name in the settlement fileMyBank
Minimum transaction amountEUR 0.01
Maximum transaction amountEUR 999,999,999.99
Session timeout5 - 30 mins
RefundFull, partial, multiple partial and over refunds are all available.
Refund Validity
ChargebackNo
Integration TypeAsynchronous
SandboxScheme-hosted

Transaction Flow

  1. The consumer selects MyBank on the merchant's checkout page.
  2. They are redirected to the PPRO-hosted bank selection page.
  3. The consumer selects the preferred bank.
  4. They enter the bank details and approve the payment.
  5. The consumer is redirected back to the merchant.

MyBank Integration

Specific input parameters for the TRANSACTION call

Field NameM/O/CTypeDescription
specin.timeoutOstringMinutes until a pending MyBank transaction times out.

Possible values: between 5 and 30

Default value: 5

For standard input parameters, see Input parameters for the TRANSACTION call.

This payment method supports the dynamic descriptor field (see The dynamic descriptor).

Specific output parameters for the TRANSACTION call

Field NameTypeDescription
SPECOUT.SRCACCOUNTHOLDERasciiThe name of the account holder

The MyBank /paymentResult endpoint returns it as buyerName.
SPECOUT.SRCBICasciiBIC of the consumer’s account

The MyBank /paymentResult endpoint returns it as buyerBankBIC.
SPECOUT.SRCIBANasciiIBAN of the consumer’s account

The MyBank /paymentResult endpoint returns it as buyerIBAN.
SPECOUT.SRCCOUNTRYasciiThe 2-letter ISO code of the country from where the consumer makes the payment. It is extracted from the IBAN.
SPECOUT.PAYMENTPURPOSEasciiThe value sent to the MyBank /initiatePayment endpoint as orderDescription.

Reflects what the consumer sees on the payment page as "Payment Purpose".

For standard output parameters, see Output parameters for the TRANSACTION call.

TRANSACTION call input

tag=mybank
&txtype=TRANSACTION
&countrycode=IT
&currency=EUR
&amount=1055
&merchanttxid=xTePFP2QyZaf
&login=johndoe
&password=wXBrpVporFVjGO4R
&contractid=JOHNDOECONTRACT
&channel=testchannel
&preferredlanguage=en
&merchantredirecturl=https%3A%2F%2Fmerchant.com%2Fwork%2Fppro2%2Flanding.php
&notificationurl=https%3A%2F%2Fmerchant.com%2Fwork%2Fppro2%2Fnotification.php
&specin.dynamicdescriptor=DynDescriptor
&accountholdername=John%20Doe
&returnmode=urlencodeext

TRANSACTION call output

REQUESTSTATUS=SUCCEEDED
STATUS=SUCCEEDED
TXID=788406252
ERRMSG=
CHANNEL=testchannel
TAG=mybank
PAYMENTGUARANTEE=NONE
REDIRECTSECRET=GC99rC1HyLkhy6pvku0WTN2gne3ZbTLV
SPECOUT_PAYMENTPURPOSE=244U453
SPECOUT_SRCCOUNTRY=IT

Branding Guidelines

Click here to access logos and other useful branding information.

Additional information

  • Some banks reject the use of a webview. Therefore, in order to maximise your MyBank authorisation rate, we recommend that your merchants do not use a webview in their mobile integration when presenting MyBank. Alternative implementations are:
    1. Redirect to external browser app
    2. Android Chrome Custom Tabs and iOS SFSafariViewController