Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Notes
Availability by Country/Currency
Payment Type | Countries | Currency | B2C | B2B |
|---|---|---|---|---|
Invoice | Germany Austria Switzerland | EUR | yes | yes |
Functional Limitations and Additional Information
Right now there are certain limitations for BS PAYONE Secure Invoice that need to be taken into account during the implementation. All information that is relevant for the merchant is summarized here.
| UI Text Box | ||
|---|---|---|
| ||
|
Shop-Plugins
In some shop systems, there is no dedicated switch for B2B/B2C transactions. To solve this, a transaction is flagged as B2B when the parameter company is filled. There is no further check, if the company name is correct.
Request "preauthorization"
During the preauthorization and authorization a risk check for the customer is performed. Depending on the result the customer qualifies or disqualifies from using this payment method. When the risk of payment default is deemed too high the transaction can’t be insured and the customer is denied, yielding an error message and the status “ERROR”.
Generally, the more customer data you send, the better the risk check can decide to give an insurance or not. Nonetheless, there following table contains flags, if a parameter is optional or not.
If the preauthorization/authorization is successful the response will contain the status “APPROVED”.
Using the Preauthorization request does NOT finalize the claim. In order to start the dunning process the transactions need to be captured first. See: capture
Please bear in mind, that a preauthorization is valid for 28 days. You need to make sure, that you capture this preauthorization in this period. Otherwise, if you know that you won’t capture the amount, please send a cancel (capture with amount=0), to free the reserved guarantee.
Request "capture"
If the transaction was initialized with a preauthorization request, you have to capture the transaction after fulfillment. The dunning process will not be started before capturing the transaction.
Since during the pilot phase not all scenarios involving multi partial capture have been tested it is recommended to only capture the full amount of the preauthorized transaction.
Request "authorization"
The authorization request simply combines both the prauthorization and the capture steps.
Remarks to API parameters
Clearingtype / Clearingsubtype
| Parameter | Value | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| fixed value "rec" | |||||||||
| clearingsubtype |
| fixed value "POV" | ||||||||
| company |
| If the company name is set the transaction will be considered B2B. There is no further check, if the company name is correct. | ||||||||
| businessrelation |
| Not mandatory by now, but strongly recommended to be used. Please use parameter "businessrelation" to specify whether the customer is a person or a company. This identifier will replace company as b2b/b2c identifier in a future version. | ||||||||
| birthday |
| Mandatory for b2c transactions. | ||||||||
| Mandatory for POV. | |||||||||
| it[n] |
| Mandatory for POV. | ||||||||
| id[n] |
| Mandatory for POV. | ||||||||
| pr[n] |
| Mandatory for POV. | ||||||||
| no[n] |
| Mandatory for POV. | ||||||||
| de[n] |
| Mandatory for POV. | ||||||||
| va[n] |
| Mandatory for POV. |
Special Test Cases
See: Secure purchase on invoice
Sequence Diagram
| draw.io Diagram | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Table of Contents | ||||
|---|---|---|---|---|
|