Partner registration
If you are looking to integrate Pay. for third parties, you can register for an account with us. Use actioncode partner in the registration process. We will prepare a customized configuration for you to start developing.
Boarding a PartnerPay. uses the My Pay portal for communication with all third parties. If you are a Payment Option Provider, Merchant, Technical integrator or Vendor, a registration must be performed and reviewed by our Boarding team.
Partner Types
Type | Description |
---|---|
Technical solution Business Partner | Creates a plugin or Hosted solution that can be used by the merchants of Pay. |
Marketing & integrations partner | Uses a plugin or hosted solution and provides support and commercial services to a merchant |
ISO | Sells the full product of Pay., including any related Business partners |
Alliance | Sells their own product, where payments are included in the total offering and necessary for a full-service offering. |
Financial Institute | Uses the product or Pay. or a subset of their products. |
Partners integration Process.
- Discover whether Pay. is the right partner for you.
- Contact a partnermanager for a eMeeting to validate.
- Signup on the Portal and get Credentials.
- Complete the boarding in full (Commercial and Compliance)
- Scope the suggested integration
- Get an implementation manager
- Discuss the API's and functionalities in scope
- Start development
- Perform self testing
- Complete certification of the integration and receive the integrationID and PartnerID.
- Publish the Integration in the Pay. network
- Connect the first (pilot) merchants
Partners need to be registeredIf you have completed the registration with PAY, you will have a M-XXXX-XXXX enrolled in our Partner Entitlement Program.
Adding the PartnerID in the stats.object
We like to monitor the transactions comming from a partner, even when the merchant changed the integrationID in there GMS. We ask you to provide in the stats.object, the PartnerID provided.
View Testcase 5: https://developer.pay.nl/docs/5-an-order-with-a-partner-integration-code
Payment Method Partner
Image and Icons
Every partner needs to povide and brand-icon set.
Naming & Labeling
You need to provide us the 'default values' for the object. You can also delivery for a specified language some adjustments.
Format | URL |
---|---|
Name | Name of the Partner as showed to other Entity in the GMS. |
Description | Short description of your proposition or company for other Entity in the GMS. |
PayerName | Name of the Partner showned on Payer level. |
PayerDescription | Short description of your proposition or company on Payer level |
Basic pricing (only for PaymentMethod partners / Acquiering entities).
You need to provide us the 'default values' for the object. You can also delivery for a specified language some adjustments.
Format | URL |
---|---|
Collecting | YES / NO / HYBRID |
Invoicing | YES / NO / HYBRID |
Basic Fee's | Per transaction Type (Sales / Refund) |
Settlement Delay | X Days |
Payment Flow | AUTH-CAPTURE or DIRECT-PAYMENT |
You can make different pricing groups, base on the county or cardtype of the Payer. If you need, then deliver per pricingScheme the details.
Rate | Per Transaction | Volume Based |
---|---|---|
Sale | € 0,25 | 1,0% |
Refund | € 0,10 | - |
Standard pricing rates or hybridYou only provide us the pricing for the standard Package. If the merchant has a Pioneer (Freemium membership), we will offer pricing according to our own needs. If the merchant has the Bussiness (Full membership) you can adjust on merchant level the pricing proposal.
Implementing & Testing
A technical integrator needs to implement technology within their own PAY. account. If the integration is completed we will publish the integration in our certified integrator list, so merchants can use the third party technology. Testing on a merchant level as a third party is not allowed.
Implementing the Test flow
After registration you receive authentication details that are necessary to load the configuration, start transaction requests and modify transactions. Starting transactions in Testmode prevents that you need to test all individual payment methods. You have to build the flow for the different statuses of a payment.
Status | Description | Action |
---|---|---|
PENDING | Payment is not completed yet, can occur when the exchange call has timed out. | Transaction is in progress, we wait for the status Update. |
DENIED | Payment Method should not be selected in the checkout again. | Please pick another payment method |
CANCEL | Payment is cancelled | You have aborted the transaction, please try again. |
AUTHORISED | Payment is authorised, products can be delivered. | Thank you for your Payment. |
VERIFY | Payment is authorised, review of the payment must be performed to set the transaction to PAID or DENIED | Thank you for your Order. |
FAILURE | Transaction is failed, due to a misconfiguration or incident with the Payment Method | Please try again or select another payment method |
Updated 3 months ago